Triple

T18307406
Position Surface form Disambiguated ID Type / Status
Subject IHO S-111 E438523 entity
Predicate usesCoordinateReference P131273 FINISHED
Object georeferenced grid 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: georeferenced grid | Statement: [IHO S-111, usesCoordinateReference, georeferenced grid]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesCoordinateReference
Context triple: [IHO S-111, usesCoordinateReference, georeferenced grid]
  • A. usesCoordinateRepresentation
    Indicates that one entity expresses or handles another entity in terms of a specific coordinate-based representation.
  • B. isReferencePointFor
    Indicates that one entity serves as a positional or conceptual basis used to locate, measure, or interpret another entity.
  • C. coordinateReferenceSystemType
    Indicates the specific kind or category of coordinate reference system (e.g., geographic, projected, vertical) associated with a spatial dataset or geometry.
  • D. hasCoordinateRole
    Indicates that one entity shares an equivalent or parallel role or function with another entity within the same context or structure.
  • E. hasCoordinates
    Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
  • F. None of above. chosen

Provenance (4 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_69d8b915e3e881909125d760c15d0c29 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e5021519a481908a9b6561946f1c65 completed April 19, 2026, 4:25 p.m.
PD Predicate disambiguation batch_69e44fdf43d08190bbcfb6b1fe3cc0ee completed April 19, 2026, 3:45 a.m.
PDg Predicate description generation batch_69e451a0ba208190a5fe92832a8f7a49 completed April 19, 2026, 3:53 a.m.
Created at: April 10, 2026, 10:35 a.m.