Triple
T4636780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edzell |
E101550
|
entity |
| Predicate | distanceToMontrose |
P57887
|
FINISHED |
| Object | approximately 14 miles north-west |
—
|
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 miles north-west | Statement: [Edzell, distanceToMontrose, approximately 14 miles north-west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMontrose Context triple: [Edzell, distanceToMontrose, approximately 14 miles north-west]
-
A.
distanceFromDenver
Indicates the measured distance between a given location and Denver.
-
B.
distanceToFortCollins
Indicates the spatial distance between a given entity’s location and the city of Fort Collins.
-
C.
distanceToGreeley
Indicates the measured distance between a given entity or location and Greeley.
-
D.
distanceToPueblo
Indicates the measured spatial distance between a given entity and the location identified as Pueblo.
-
E.
distanceToMountRushmore
Indicates the measured or calculated spatial distance between an entity and Mount Rushmore.
- 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_69bd43d2f1c081908cd4b7ec48ecc73d |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a62a9e48190b0cf1cbcc51f00c0 |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5233cb5081908807e2b150f0ca06 |
completed | March 20, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69bd56f7b94481909f3335312becd446 |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:13 p.m.