Triple
T518660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eddington–Finkelstein coordinates |
E10764
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coordinate system in general relativity |
C2466
|
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 in general relativity Context triple: [Eddington–Finkelstein coordinates, instanceOf, coordinate system in general relativity]
-
A.
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.
-
B.
cosmological collapse solution
A cosmological collapse solution is a spacetime model in general relativity or cosmology in which the universe (or a region of it) evolves from expansion or equilibrium into a contracting phase that culminates in a singularity or high-density end state.
-
C.
circle of latitude
A circle of latitude is an imaginary horizontal line encircling the Earth, connecting all points at the same angular distance north or south of the Equator.
-
D.
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.
-
E.
location
A location is a specific place or position in physical or virtual space that can be identified, referenced, and used to describe where entities or events exist or occur.
- 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_69a2e84a0d08819087e01863fcd9abf1 |
completed | Feb. 28, 2026, 1:06 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.