Triple
T20860443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ordnance Survey trig pillar |
E513602
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geodetic triangulation station |
C20364
|
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: geodetic triangulation station Context triple: [Ordnance Survey trig pillar, instanceOf, geodetic triangulation station]
-
A.
geodetic reference point
chosen
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.
-
B.
geodetic survey
A geodetic survey is a precise method of measuring and mapping large areas of the Earth's surface that accounts for its curvature and gravitational variations to establish accurate positions, elevations, and reference frameworks.
-
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 standard
A geodetic standard is an agreed-upon reference framework, model, or set of conventions used to define positions, shapes, and measurements on or near the Earth’s surface consistently and accurately.
-
E.
geodetic datum component
A geodetic datum component is an individual element (such as an ellipsoid, reference frame, or coordinate system parameter) that contributes to defining the position, orientation, and scale of a geodetic datum used for spatial referencing on or near the Earth’s surface.
- 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:44 p.m.