Triple
T14506443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penrose spin networks |
E340275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | concept in mathematical physics |
C14587
|
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: concept in mathematical physics Context triple: [Penrose spin networks, instanceOf, concept in mathematical physics]
-
A.
result in mathematical physics
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.
-
B.
concept in vector calculus
A concept in vector calculus is an abstract idea or principle involving vector-valued functions and operations—such as gradients, divergences, curls, and line or surface integrals—that describes how quantities with both magnitude and direction vary in space.
-
C.
Physical concept
chosen
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.
-
D.
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.
-
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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:21 a.m.