Triple
T28184842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keyhole Route |
E716148
|
entity |
| Predicate | roundTripDistance |
P35279
|
FINISHED |
| Object | approximately 14 to 15 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 14 to 15 miles | Statement: [Keyhole Route, roundTripDistance, approximately 14 to 15 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roundTripDistance Context triple: [Keyhole Route, roundTripDistance, approximately 14 to 15 miles]
-
A.
approximateRoundTripDistanceFromTrailhead
chosen
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
B.
flightDistance
Indicates the measured distance covered by a flight between its origin and destination.
-
C.
returnJourneyLength
Indicates the total distance or duration of a journey back from a destination to its point of origin.
-
D.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
E.
numberOfDailyRoundTrips
Indicates the total count of round-trip journeys performed per day in the described context.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a931748190a637e631a52bbfaa |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 27, 2026, 10:22 p.m.