Triple

T19450103
Position Surface form Disambiguated ID Type / Status
Subject Airy 1830 ellipsoid E486592 entity
Predicate geodeticDatumType P125470 FINISHED
Object local datum ellipsoid LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: local datum ellipsoid | Statement: [Airy 1830 ellipsoid, geodeticDatumType, local datum ellipsoid]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: geodeticDatumType
Context triple: [Airy 1830 ellipsoid, geodeticDatumType, local datum ellipsoid]
  • A. coordinateReferenceSystemType
    Indicates the specific kind or category of coordinate reference system (e.g., geographic, projected, vertical) associated with a spatial dataset or geometry.
  • B. isLocalDatumEllipsoid chosen
    Indicates that a geodetic datum is defined relative to a specific local reference ellipsoid rather than a global one.
  • C. gridReferenceType
    Indicates the specific system or format used to express a location’s position within a spatial grid.
  • D. hasGeodeticPurpose
    Indicates that something is associated with or serves a specific geodetic purpose, such as measurement, reference, or positioning in geodesy.
  • E. datumUsed
    Indicates that a particular piece of data is utilized or referenced in performing an action, process, or relation.
  • F. None of above.

Provenance (3 batches)

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_69d8e8d7ad488190a3373045029b0f3b completed April 10, 2026, 12:11 p.m.
NER Named-entity recognition batch_69e6338caeb48190aeb1d511996984e3 completed April 20, 2026, 2:09 p.m.
PD Predicate disambiguation batch_69e4fd6e806081909053f325ba01ab6b completed April 19, 2026, 4:06 p.m.
Created at: April 10, 2026, 1:38 p.m.