Triple
T28621957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyakov action in string theory |
E724407
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | string theory formalism |
C26179
|
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: string theory formalism Context triple: [Polyakov action in string theory, instanceOf, string theory formalism]
-
A.
string theory concept
A string theory concept is an abstract element within the theoretical framework of string theory that represents fundamental entities, interactions, or symmetries as manifestations of one-dimensional vibrating strings in higher-dimensional spacetime.
-
B.
formalism for physics
chosen
A formalism for physics is a structured mathematical and conceptual framework used to represent, analyze, and predict physical phenomena.
-
C.
theory in field theory
A theory in field theory is a specific, mathematically formulated model that assigns fields and their dynamics to spacetime, defining how physical quantities evolve and interact according to a chosen set of principles and equations.
-
D.
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.
-
E.
gauge theory
A gauge theory is a type of field theory in which the laws of physics are invariant under continuous local transformations of certain internal symmetries, leading to the introduction of gauge fields that mediate fundamental interactions.
- 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.