Triple
T9637357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infeld–van der Waerden formalism |
E232967
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | spinor formalism |
C18224
|
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: spinor formalism Context triple: [Infeld–van der Waerden formalism, instanceOf, spinor formalism]
-
A.
pseudo-Riemannian manifold
A pseudo-Riemannian manifold is a smooth manifold equipped with a nondegenerate, symmetric metric tensor of arbitrary signature that allows measurement of lengths and angles, including those with indefinite sign as in spacetime geometry.
-
B.
spacetime
Spacetime is the four-dimensional continuum that unifies the three dimensions of space with time into a single geometric framework in which all physical events occur.
-
C.
Lorentzian manifold
A Lorentzian manifold is a smooth manifold equipped with a metric tensor of signature \((-+\cdots+)\) (or its variants) that models spacetime in general relativity by distinguishing timelike, spacelike, and null directions.
-
D.
polarization formalism
Polarization formalism is a theoretical framework that mathematically represents and analyzes the polarization state of waves (such as light) and their transformations through optical systems.
-
E.
representation of the Lorentz group
chosen
A representation of the Lorentz group is a mathematical structure (typically a vector space with linear operators) on which the Lorentz transformations act in a way that preserves the group operations, allowing physical fields or states to transform consistently under changes of inertial reference frames.
- 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_69ca848940cc8190b97cec654cb3bb4a |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:11 p.m.