Triple
T20690777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Witten–Reshetikhin–Turaev invariant |
E508543
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | quantum invariant |
C43444
|
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 invariant Context triple: [Witten–Reshetikhin–Turaev invariant, instanceOf, quantum invariant]
-
A.
topological quantum field theory
A topological quantum field theory is a quantum field theory whose observables and correlation functions depend only on the topology of the underlying spacetime manifold, not on its geometric details such as distances or angles.
-
B.
homological invariant
A homological invariant is a quantity or structure derived from homology theory that remains unchanged under specified transformations, used to distinguish and classify mathematical objects up to an appropriate notion of equivalence.
-
C.
geometric invariant
A geometric invariant is a property of a geometric object that remains unchanged under a specified group of transformations, such as rotations, translations, or more general symmetries.
-
D.
classical invariant
A classical invariant is a quantity or property associated with a mathematical object that remains unchanged under a specified group of classical transformations, such as rotations, translations, or linear changes of coordinates.
-
E.
problem in invariant theory
A problem in invariant theory concerns determining and characterizing the algebraic functions (invariants) that remain unchanged under the action of a given group on a vector space or algebraic variety.
- F. None of above. chosen
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_69e0b4c1ed408190b72dd26b1e33f8a1 |
completed | April 16, 2026, 10:06 a.m. |
Created at: April 16, 2026, 12:08 p.m.