Triple

T5555473
Position Surface form Disambiguated ID Type / Status
Subject Horseshoe Bend E145627 entity
Predicate distanceFromUS89 P64450 FINISHED
Object about 1.5 miles from U.S. Route 89 parking area 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: about 1.5 miles from U.S. Route 89 parking area | Statement: [Horseshoe Bend, distanceFromUS89, about 1.5 miles from U.S. Route 89 parking area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distanceFromUS89
Context triple: [Horseshoe Bend, distanceFromUS89, about 1.5 miles from U.S. Route 89 parking area]
  • A. distanceFromDesMoines
    Indicates the physical distance between a given location and the city of Des Moines.
  • B. distanceToWinnemucca
    Indicates the spatial distance between a given entity’s location and the location of Winnemucca.
  • C. isNearestI95BorderCrossingTo
    Indicates that one location is the closest border crossing point to Interstate 95 relative to another specified reference location.
  • D. distanceFromHanaTown (miles)
    Indicates the number of miles separating a given place or entity from Hana Town.
  • E. approximateDistanceFromHighway1
    Indicates the estimated distance between a location and Highway 1, rather than an exact measured value.
  • 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_69c008fcaf788190bafa02a1917ee73b completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c01ffc5e7c81908e1c454d3bfd357b completed March 22, 2026, 4:59 p.m.
PD Predicate disambiguation batch_69c01b10bbf8819098655839c03b7832 completed March 22, 2026, 4:38 p.m.
PDg Predicate description generation batch_69c01f0684908190ae2d14f0bd2ab892 completed March 22, 2026, 4:55 p.m.
Created at: March 22, 2026, 3:36 p.m.