Triple

T24684436
Position Surface form Disambiguated ID Type / Status
Subject Chepultepec E611239 entity
Predicate hasGeographicCoordinates P10142 FINISHED
Object approximately 33.915°N 86.516°W 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: approximately 33.915°N 86.516°W | Statement: [Chepultepec, hasGeographicCoordinates, approximately 33.915°N 86.516°W]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasGeographicCoordinates
Context triple: [Chepultepec, hasGeographicCoordinates, approximately 33.915°N 86.516°W]
  • A. hasGeographicalCoordinateSystem
    Indicates that something uses or is defined within a specific geographical coordinate system for locating positions on the Earth’s surface.
  • B. hasGeocode
    Indicates that an entity is associated with a specific geographic coordinate or coded location reference.
  • C. hasCoordinates chosen
    Indicates that an entity is associated with specific spatial coordinates that define its position in a given reference system.
  • D. hasGeographicBasis
    Indicates that something is grounded in, derived from, or defined by a particular geographic location or area.
  • E. hasGeographicType
    Indicates that an entity is associated with or classified by a specific type or category of geographic feature or area.
  • 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_69e2c4d678b081908910f4271627a31a completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f44a417a58819081777e18dda149fd completed May 1, 2026, 6:37 a.m.
PD Predicate disambiguation batch_69f442a977b08190b44eac040cb90211 completed May 1, 2026, 6:05 a.m.
Created at: April 18, 2026, 3:17 a.m.