Triple
T17105476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 't Hooft anomaly |
E415088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | quantum field theory concept |
C32088
|
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: quantum field theory concept Context triple: ['t Hooft anomaly, instanceOf, quantum field theory concept]
-
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.
quantum mechanical concept
A quantum mechanical concept is an abstract idea or principle that describes the behavior, properties, or interactions of physical systems at atomic and subatomic scales, where phenomena are governed by the rules of quantum theory rather than classical physics.
-
C.
problem in field theory
A problem in field theory is a conceptual or computational question involving the properties, structures, and interactions of fields—such as scalar, vector, or gauge fields—typically formulated within the framework of classical or quantum field theory.
-
D.
field theory concept
chosen
A field theory concept is an abstract idea or construct used to describe and analyze physical systems in terms of fields—quantities defined at every point in space and time—such as electromagnetic, gravitational, or quantum fields.
-
E.
fermionic field
A fermionic field is a quantum field whose excitations correspond to particles with half-integer spin that obey Fermi–Dirac statistics and the Pauli exclusion principle.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:35 a.m.