Triple
T8070256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KFAT |
E188351
|
entity |
| Predicate | distanceToYosemiteNationalPark |
P80337
|
FINISHED |
| Object | approximately 65 miles south |
—
|
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 65 miles south | Statement: [KFAT, distanceToYosemiteNationalPark, approximately 65 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToYosemiteNationalPark Context triple: [KFAT, distanceToYosemiteNationalPark, approximately 65 miles south]
-
A.
distanceToSequoiaNationalParkEntrance
Indicates the physical distance between a given location and the entrance of Sequoia National Park.
-
B.
distanceToWitney
Indicates the spatial distance between an entity and the location Witney.
-
C.
distanceFromSanJosé
Indicates the measured spatial distance between a given entity and the location of San José.
-
D.
distanceToYellowstoneEastEntrance
Indicates the measured distance from a given location or entity to the east entrance of Yellowstone National Park.
-
E.
distanceToSanJosé
Indicates the spatial distance between a given entity and the location of San José.
- 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_69ca82b42674819086840efea12478e5 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3ffe29188190834ec4f71043a99d |
completed | March 31, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69cb049cd51c8190bb3b0f503e42fa8d |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14be17208190bb51c3dfcb613f20 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:27 p.m.