Triple
T28621956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyakov action in string theory |
E724407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | action functional in theoretical physics |
C24250
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: action functional in theoretical physics Context triple: [Polyakov action in string theory, instanceOf, action functional in theoretical physics]
-
A.
action functional
chosen
An action functional is a mapping from possible configurations or paths of a physical system to a real number, whose extremization yields the system’s equations of motion via the principle of least action.
-
B.
formalism for physics
A formalism for physics is a structured mathematical and conceptual framework used to represent, analyze, and predict physical phenomena.
-
C.
theory in theoretical physics
A theory in theoretical physics is a mathematically formulated, logically consistent framework that explains and predicts physical phenomena by modeling fundamental entities and their interactions.
-
D.
theorem in theoretical physics
A theorem in theoretical physics is a rigorously proven statement, derived from fundamental physical principles and mathematical formalism, that holds universally within the specified theoretical framework.
-
E.
regularization scheme in quantum field theory
A regularization scheme in quantum field theory is a systematic procedure for modifying divergent integrals or sums—typically by introducing an auxiliary parameter or cutoff—so that they become finite and mathematically well-defined while preserving as much of the theory’s symmetry and structure as possible.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
Created at: April 28, 2026, 4:34 a.m.