Triple
T20324191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoehne, Colorado |
E492288
|
entity |
| Predicate | distanceToTrinidad |
P139681
|
FINISHED |
| Object | approximately 11 miles northeast |
—
|
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 11 miles northeast | Statement: [Hoehne, Colorado, distanceToTrinidad, approximately 11 miles northeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToTrinidad Context triple: [Hoehne, Colorado, distanceToTrinidad, approximately 11 miles northeast]
-
A.
distanceToJamaica
Indicates the measured or calculated distance between a given entity and the location Jamaica.
-
B.
distanceFromPortOfSpain
Indicates the measured distance between a given location and the city of Port of Spain.
-
C.
distanceToHaiti
Indicates the measured or calculated spatial distance between a given entity or location and the country of Haiti.
-
D.
distanceFromSantoDomingo
Indicates the spatial distance between a given entity and the location of Santo Domingo.
-
E.
distanceToPort-au-Prince
Indicates the spatial distance between a given location and the city of Port-au-Prince.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778e59508190bfd7a3ce44d56a93 |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
| PDg | Predicate description generation | batch_69e58d7481508190a87c8b88f9df9879 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 16, 2026, 11:21 a.m.