Triple
T17585168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CERN reference frame |
E428302
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | reference frame |
C5801
|
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: reference frame Context triple: [CERN reference frame, instanceOf, reference frame]
-
A.
global reference frame
chosen
A global reference frame is a fixed, overarching coordinate system used to consistently define positions, orientations, and motions of objects throughout an entire modeled world or environment.
-
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.
coordinate system in general relativity
A coordinate system in general relativity is a smooth, arbitrary labeling of spacetime events by numerical values that allows the mathematical description of physical laws while having no intrinsic physical significance itself.
-
D.
object in special relativity
An object in special relativity is any physical entity whose properties—such as length, time intervals, and mass—transform between inertial reference frames according to the Lorentz transformations, ensuring the constancy of the speed of light and the invariance of physical laws.
-
E.
Eddington–Finkelstein coordinate system
The Eddington–Finkelstein coordinate system is a reformulation of the Schwarzschild spacetime using null (lightlike) coordinates that smoothly extend across the event horizon, eliminating the coordinate singularity present in standard Schwarzschild coordinates.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:50 a.m.