Triple
T33579980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stone–von Neumann theorem |
E860124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theorem in mathematical physics |
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: theorem in mathematical physics Context triple: [Stone–von Neumann theorem, instanceOf, theorem in mathematical physics]
-
A.
theorem in theoretical physics
A theorem in theoretical physics is a rigorously proven statement, derived from fundamental physical principles and mathematical formalism, that holds universally within the specified theoretical framework.
-
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.
mathematical theorem
A mathematical theorem is a rigorously proven statement derived from axioms and previously established results, expressing a fundamental truth within a formal mathematical system.
-
D.
mathematical condition in physics
A mathematical condition in physics is a precise quantitative requirement or constraint, typically expressed as an equation or inequality, that physical quantities must satisfy for a theory, law, or model to hold.
-
E.
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.
- 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_69f3497d37848190afcbb5ef3f5c7376 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:40 a.m.