Triple
T21248127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fruita |
E523670
|
entity |
| Predicate | distanceTo Grand Junction (approx. miles) |
P143359
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Fruita, distanceTo Grand Junction (approx. miles), 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceTo Grand Junction (approx. miles) Context triple: [Fruita, distanceTo Grand Junction (approx. miles), 10]
-
A.
distanceFromMoab
Indicates the measured distance separating a given entity or location from Moab.
-
B.
distanceFromDenver
Indicates the measured distance between a given location and Denver.
-
C.
distanceFromSaltLakeCity
Indicates the measured distance between a given location and Salt Lake City.
-
D.
distanceToPueblo
Indicates the measured spatial distance between a given entity and the location identified as Pueblo.
-
E.
distanceFromJasper
Indicates the spatial distance measured from the reference point or entity named Jasper to another entity or location.
- 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_69e0b5146c108190adc9adb73e90abff |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7359b756c819085480ca4174c53c2 |
completed | April 21, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f9943ed881909ef49045c5bcf6df |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3:55 p.m.