Triple

T10378090
Position Surface form Disambiguated ID Type / Status
Subject NAVD 88 E244556 entity
Predicate coordinateReferenceFrameRelation P12083 FINISHED
Object compatible with NAD 83 horizontal datum 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: compatible with NAD 83 horizontal datum | Statement: [NAVD 88, coordinateReferenceFrameRelation, compatible with NAD 83 horizontal datum]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: coordinateReferenceFrameRelation
Context triple: [NAVD 88, coordinateReferenceFrameRelation, compatible with NAD 83 horizontal datum]
  • A. datumRelation chosen
    Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
  • B. spatialRelation
    Indicates a spatial relationship between entities, specifying how one is positioned or located relative to another in space.
  • C. isReferencePointFor
    Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
  • D. gridReferenceType
    Indicates the specific system or format used to express a location’s position within a spatial grid.
  • E. transformationRelation
    Indicates a relationship where one entity is changed, converted, or transformed into another entity or state.
  • 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_69d381b3e328819094b23b8edcd29b5a completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4e98f312481909f7276fc3762d7bc completed April 7, 2026, 11:25 a.m.
PD Predicate disambiguation batch_69d4dface5508190a7b42f01ad0a19a2 completed April 7, 2026, 10:42 a.m.
Created at: April 6, 2026, 12:03 p.m.