Triple
T7483118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Rim |
E176810
|
entity |
| Predicate | distanceFromSouthRimByRoad |
P43472
|
FINISHED |
| Object | approximately 210 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 210 miles | Statement: [North Rim, distanceFromSouthRimByRoad, approximately 210 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromSouthRimByRoad Context triple: [North Rim, distanceFromSouthRimByRoad, approximately 210 miles]
-
A.
distanceToGrandCanyonSouthRim
chosen
Indicates the physical distance between a given location or entity and the Grand Canyon’s South Rim.
-
B.
approximateRoundTripDistanceFromTrailhead
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
C.
distanceToPerisherByRoad
Indicates the road travel distance required to reach Perisher from a given location.
-
D.
distanceToFlagstaff
Indicates the measured distance between a given entity’s location and the location of Flagstaff.
-
E.
distanceFromTucson
Indicates the spatial distance between a given entity and the location of Tucson.
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f53923e4819081bf79ed962a971c |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:42 p.m.