Triple
T5273861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | topological quantum field theory |
E119326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mathematical physics concept |
C15689
|
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: mathematical physics concept Context triple: [topological quantum field theory, instanceOf, mathematical physics concept]
-
A.
Physical concept
A physical concept is an abstract idea or principle that describes, explains, or quantifies phenomena in the physical world, such as force, energy, or motion.
-
B.
result in mathematical physics
chosen
A result in mathematical physics is a rigorously proven statement that connects precise mathematical structures with physical theories, often clarifying, justifying, or predicting phenomena within a formal framework.
-
C.
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.
-
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.
concept in classical electromagnetism
A concept in classical electromagnetism represents a fundamental idea or quantity—such as electric field, magnetic flux, or charge—that describes how electric and magnetic phenomena are generated, interact, and propagate in space and time.
- 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_69bd446c38e081908cdaf113bdf86790 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:51 p.m.