Triple

T11331193
Position Surface form Disambiguated ID Type / Status
Subject Chimborazo E268346 entity
Predicate reasonForFarthestPoint P98543 FINISHED
Object Earth’s equatorial bulge 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: Earth’s equatorial bulge | Statement: [Chimborazo, reasonForFarthestPoint, Earth’s equatorial bulge]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: reasonForFarthestPoint
Context triple: [Chimborazo, reasonForFarthestPoint, Earth’s equatorial bulge]
  • A. reasonForLocation
    Indicates the cause, purpose, or justification for why an entity is at a particular location.
  • B. isMostDistantHumanMadeObject
    Indicates that the subject is the human-made object currently farthest from Earth (or from its point of origin).
  • C. nearestPointTo
    Indicates the point that is closest in distance to a given reference point or object among a set of candidates.
  • D. reasonForLatitude
    Indicates that one factor or circumstance serves as the explanation or cause for a particular degree or extent of latitude (freedom, variation, or deviation) in a situation or condition.
  • E. maximumReach
    Indicates the greatest extent, distance, or limit that something can reach or influence within a given context.
  • 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_69d6aacb1f0881908c84a349fd1be047 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9fd38308190a5458be1bfcc89ea completed April 9, 2026, 6:03 p.m.
PD Predicate disambiguation batch_69d787afe5a48190b8af1a3e19529641 completed April 9, 2026, 11:04 a.m.
PDg Predicate description generation batch_69d796d049e88190a9fd7508f477f541 completed April 9, 2026, 12:08 p.m.
Created at: April 8, 2026, 9:32 p.m.