Triple
T29734308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type IIA string theory |
E752413
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | supersymmetric theory |
C12955
|
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: supersymmetric theory Context triple: [Type IIA string theory, instanceOf, supersymmetric theory]
-
A.
symmetry in quantum field theory
Symmetry in quantum field theory is a transformation of fields that leaves the action or Lagrangian invariant, leading to conserved quantities and powerful constraints on particle interactions and dynamics.
-
B.
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.
-
C.
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.
-
D.
theory in theoretical physics
chosen
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.
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.
- 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:44 p.m.