Triple
T15745362
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hualapai Hilltop trailhead |
E381708
|
entity |
| Predicate | distanceToSupaiVillage |
P52833
|
FINISHED |
| Object | approximately 8 miles by trail |
—
|
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 8 miles by trail | Statement: [Hualapai Hilltop trailhead, distanceToSupaiVillage, approximately 8 miles by trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSupaiVillage Context triple: [Hualapai Hilltop trailhead, distanceToSupaiVillage, approximately 8 miles by trail]
-
A.
approximateDistanceFromSupai
chosen
Indicates the estimated spatial distance between a given entity or location and Supai.
-
B.
distanceFromMoab
Indicates the measured distance separating a given entity or location from Moab.
-
C.
distanceToPueblo
Indicates the measured spatial distance between a given entity and the location identified as Pueblo.
-
D.
distanceToTownOfShiprock
Indicates the measured distance between a given location and the town of Shiprock.
-
E.
distanceToSedona
Indicates the measured or calculated spatial distance between a given entity’s location and the location of Sedona.
- 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_69d86d9e6b44819085d1f6a969ecb74c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4d6b5788190883746ee82c799f5 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e0052c6208819098165d61d378d13b |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:46 a.m.