[KongchangAI]
Other

Language Model

Core Facts

Timeline (last 90 days)

Oct 23

The same model performs vastly differently across Agent products, and the gap lies mainly not in the model but in the scaffolding built around it (loop control, tool integration, etc.).

Unverified50%
Oct 23

Simulated control evaluations (SCEs) use language models to simulate tool responses in place of a real execution environment, allowing control evaluations to be flexibly constructed for specific deployment scenarios.

Unverified50%
Oct 22

A language model itself can only output text and cannot directly perform operations such as opening files or pressing buttons.

Unverified60%
Oct 21

The leap in language model capabilities is obvious to all, but general-purpose robots that can stably complete household, warehousing and assembly tasks remain at the laboratory and demo-video stage.

Unverified50%
Oct 20

The core idea of using language models for protein sequence generation is to treat amino acid sequences as text composed of 20 letters and perform autoregressive or masked pretraining on large-scale protein sequence databases.

Unverified50%
Oct 19

The model outputs the most "likely" continuation token by token by probability rather than verifying whether a package actually exists in the npm registry, so package names, function signatures, and API version numbers are high-hallucination areas.

Unverified50%
Oct 19

In small-model applications, everything that must be exact (such as deadlines, amounts, reference numbers, issuing institutions) should be handled by deterministic code, and everything that needs to be understood (such as explaining the letter) should be left to the model.

Unverified50%
Oct 19

When a language model generates text, it predicts only the next token at each step, and a token may be a whole word, a word fragment, punctuation, or a word with a leading space.

Unverified50%
Oct 19

Current language models mainly rely on offline training and maximum likelihood estimation, lacking theoretical guarantees for online continual learning behavior.

Unverified50%
Oct 18

In BLACKBOX, the language model is responsible for choosing tools, interpreting graph query results, synthesizing evidence, and generating fault explanations, but the graph always remains the source of operations facts.

Unverified50%

40 more timeline events

All Facts (20)

Verified

Large language models are essentially stateless functions whose weights are fixed at inference time and do not learn over time.

80%
Verified

The Agent Harness does not replace the reasoning capability of the core model, but instead builds a runtime management shell around the model, responsible for cross-cutting concerns such as tool invocation, state management, and error recovery.

80%
Verified

Current mainstream large language models exhibit significant deficiencies in both confidence calibration and selective abstention, tend to be overconfident, and when faced with questions outside the training distribution, tend to produce fluent but incorrect answers.

65%
Verified

Large language models cannot structurally distinguish between user instructions and instructions embedded in content, because both are part of the same token sequence from the model's perspective.

65%
Verified

Reward model training can use learning-to-rank frameworks such as the Bradley-Terry model, training a neural network to predict the probability of human preference between any two responses, taking a (prompt, response) pair as input and outputting a scalar score.

65%
Verified

The tool-calling mechanism allows large language models to dynamically invoke external functions during inference, representing a fundamental leap from language models to action models.

65%
Unverified

A language model itself can only output text and cannot directly perform operations such as opening files or pressing buttons.

60%
Unverified

This article is compiled from automatically generated content; the original text was drafted by a language model and checked automatically, with no human author credited.

60%
Unverified

The larger the parameter count, the stronger a model generally is in language understanding and generation quality, but the memory and compute requirements also increase proportionally.

60%
Unverified

The same model performs vastly differently across Agent products, and the gap lies mainly not in the model but in the scaffolding built around it (loop control, tool integration, etc.).

50%
Unverified

Simulated control evaluations (SCEs) use language models to simulate tool responses in place of a real execution environment, allowing control evaluations to be flexibly constructed for specific deployment scenarios.

50%
Unverified

The leap in language model capabilities is obvious to all, but general-purpose robots that can stably complete household, warehousing and assembly tasks remain at the laboratory and demo-video stage.

50%
Unverified

The core idea of using language models for protein sequence generation is to treat amino acid sequences as text composed of 20 letters and perform autoregressive or masked pretraining on large-scale protein sequence databases.

50%
Unverified

The model outputs the most "likely" continuation token by token by probability rather than verifying whether a package actually exists in the npm registry, so package names, function signatures, and API version numbers are high-hallucination areas.

50%
Unverified

In small-model applications, everything that must be exact (such as deadlines, amounts, reference numbers, issuing institutions) should be handled by deterministic code, and everything that needs to be understood (such as explaining the letter) should be left to the model.

50%
Unverified

When a language model generates text, it predicts only the next token at each step, and a token may be a whole word, a word fragment, punctuation, or a word with a leading space.

50%
Unverified

Current language models mainly rely on offline training and maximum likelihood estimation, lacking theoretical guarantees for online continual learning behavior.

50%
Unverified

In BLACKBOX, the language model is responsible for choosing tools, interpreting graph query results, synthesizing evidence, and generating fault explanations, but the graph always remains the source of operations facts.

50%
Unverified

Deterministic orchestration demotes the model to a stateless function call that receives only the current sub-problem and returns structured output, holding no cross-round memory.

50%
Unverified

The three failure modes of dropped steps, narration instead of execution, and empty turns appear in exactly the same way on large and small models, and the common factor is the agentic loop itself rather than model scale.

50%

Source Articles