Triple
T11032457
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Double O Arch |
E260789
|
entity |
| Predicate | trailDistanceRoundTrip |
P35279
|
FINISHED |
| Object | approximately 7.2 miles |
—
|
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 7.2 miles | Statement: [Double O Arch, trailDistanceRoundTrip, approximately 7.2 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trailDistanceRoundTrip Context triple: [Double O Arch, trailDistanceRoundTrip, approximately 7.2 miles]
-
A.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
B.
tourLength
Indicates the total duration or distance covered by a tour or route.
-
C.
approximateRoundTripDistanceFromTrailhead
chosen
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
D.
distanceTraveled
Indicates the total length of the path an entity has moved over a period of time or between two points.
-
E.
totalRouteLength
Indicates the overall distance or length of an entire route when all its segments are combined.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e650b48190967c53f54e3464ad |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.