Triple
T8688434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth parallels system |
E206224
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geographic coordinate system component |
C15093
|
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: geographic coordinate system component Context triple: [Earth parallels system, instanceOf, geographic coordinate system component]
-
A.
geodetic coordinate system
chosen
A geodetic coordinate system is a reference framework that specifies locations on or near the Earth's surface using latitude, longitude, and often height relative to a defined ellipsoidal model of the Earth.
-
B.
projected coordinate system
A projected coordinate system is a spatial reference framework that represents locations on the curved surface of the Earth using a flat, two-dimensional map projection with defined units, origin, and projection parameters.
-
C.
geodetic datum
A geodetic datum is a reference framework consisting of a defined origin, orientation, and scale used to precisely locate points on the Earth’s surface in terms of latitude, longitude, and elevation.
-
D.
geodetic reference point
A geodetic reference point is a precisely surveyed physical location on the Earth's surface used as a fixed coordinate reference for mapping, surveying, and geospatial measurements.
-
E.
celestial coordinate system
A celestial coordinate system is a framework for specifying the positions of objects in the sky using angular measurements relative to defined reference planes and points, such as the celestial equator and poles.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.