Triple
T1463311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lorentz contraction |
E31562
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | effect in special relativity |
C7236
|
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: effect in special relativity Context triple: [Lorentz contraction, instanceOf, effect in special relativity]
-
A.
relativistic wave equation
A relativistic wave equation is a differential equation, such as the Klein–Gordon or Dirac equation, that describes how quantum fields or particles evolve in space and time in a way consistent with the principles of special relativity.
-
B.
object in general relativity
An object in general relativity is any localized concentration of energy–momentum whose presence curves spacetime and thereby influences the motion of matter and light.
-
C.
momentum conservation paradox
A momentum conservation paradox is an apparent contradiction in a physical scenario where the total momentum seems not to be conserved, typically arising from incomplete analysis, neglected interactions, or misapplied reference frames.
-
D.
solution in general relativity
A solution in general relativity is a specific spacetime metric (and accompanying matter fields, if any) that satisfies Einstein’s field equations for a given physical configuration or set of conditions.
-
E.
photon correlation effect
Photon correlation effect is the phenomenon where statistical correlations between detected photons reveal underlying properties of a light source, such as coherence, quantum statistics, and emission dynamics.
- 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_69a49917dfc081909acdbdf5d684f1ef |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 8 p.m.