Triple
T28622004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polyakov action |
E724408
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | string theory action |
C17865
|
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 action Context triple: [Polyakov action, instanceOf, string theory action]
-
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.
Lagrangian density
chosen
The Lagrangian density is a function of fields and their derivatives defined over spacetime whose integral (the action) determines the dynamics of a physical system via the principle of least action.
-
C.
supergravity background
A supergravity background is a specific solution of supergravity field equations that defines a curved spacetime (often with fluxes and additional fields) in which strings or branes consistently propagate.
-
D.
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.
-
E.
supergravity solution
A supergravity solution is a specific configuration of fields (including the metric and superpartner fields) that satisfies the coupled equations of motion of a supergravity theory, often representing extended objects like branes or black holes in a higher-dimensional spacetime.
- 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.