Triple

T7881509
Position Surface form Disambiguated ID Type / Status
Subject South Entrance near Grand Teton E182988 entity
Predicate positionRelativeToYellowstone P79544 FINISHED
Object southern boundary 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: southern boundary | Statement: [South Entrance near Grand Teton, positionRelativeToYellowstone, southern boundary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: positionRelativeToYellowstone
Context triple: [South Entrance near Grand Teton, positionRelativeToYellowstone, southern boundary]
  • A. distanceToYellowstoneEastEntrance
    Indicates the measured distance from a given location or entity to the east entrance of Yellowstone National Park.
  • B. positionRelativeToNiagaraFalls
    Indicates the spatial relationship of an entity’s location with respect to Niagara Falls, such as its direction, distance, or relative placement.
  • C. positionRelativeToSummit
    Indicates the spatial relationship of an entity’s location with respect to the summit of a feature or structure.
  • D. distanceToOldFaithfulGeyser
    Indicates the spatial distance between a given entity and the Old Faithful Geyser.
  • E. distanceFromDenver
    Indicates the measured distance between a given location and Denver.
  • 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_69ca828af6e48190a06ee7010d8f0e64 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb39c14a188190a225ca3c7e515b0c completed March 31, 2026, 3:04 a.m.
PD Predicate disambiguation batch_69cae92b0cd881908e715a10d3252e83 completed March 30, 2026, 9:20 p.m.
PDg Predicate description generation batch_69caf786ec748190b6347b0c94335550 completed March 30, 2026, 10:21 p.m.
Created at: March 30, 2026, 4:58 p.m.