Triple
T656138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kruskal–Szekeres coordinates |
E11652
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coordinate system |
C2467
|
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: coordinate system Context triple: [Kruskal–Szekeres coordinates, instanceOf, coordinate system]
-
A.
coordinate transformation
A coordinate transformation is a mathematical operation that converts the representation of points or vectors from one coordinate system to another while preserving their underlying geometric relationships.
-
B.
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.
-
C.
spacetime coordinate chart
chosen
A spacetime coordinate chart is a mapping that assigns a unique set of numerical coordinates to each event in a region of spacetime, providing a local reference frame for describing physical phenomena.
-
D.
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.
-
E.
system of equations
A system of equations is a set of two or more equations with the same variables that are considered simultaneously to find values satisfying all of them at once.
- 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_69a4932862a0819098be659c814e4981 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.