Triple
T16745416
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton, Montana |
E406937
|
entity |
| Predicate | distanceToMissoula |
P124475
|
FINISHED |
| Object | approximately 45–50 miles south of Missoula |
—
|
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 45–50 miles south of Missoula | Statement: [Hamilton, Montana, distanceToMissoula, approximately 45–50 miles south of Missoula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMissoula Context triple: [Hamilton, Montana, distanceToMissoula, approximately 45–50 miles south of Missoula]
-
A.
distanceToBoise
Indicates the spatial distance between a given entity’s location and the city of Boise.
-
B.
distanceToSiouxCity
Indicates the spatial distance between a given entity and the location of Sioux City.
-
C.
distanceToSiouxFalls
Indicates the spatial distance between a given entity and the location of Sioux Falls.
-
D.
distanceToSaltLakeCity
Indicates the measured or calculated distance between a given entity’s location and the city of Salt Lake City.
-
E.
distanceToWichita
Indicates the measured distance between a given entity’s location and the city of Wichita.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3aa223aa88190a3c1805ece7317e2 |
completed | April 18, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:21 a.m.