Triple
T24641986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lamoille, Nevada |
E609991
|
entity |
| Predicate | distanceToElko |
P156880
|
FINISHED |
| Object | approximately 20 miles southeast of Elko, Nevada |
—
|
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 20 miles southeast of Elko, Nevada | Statement: [Lamoille, Nevada, distanceToElko, approximately 20 miles southeast of Elko, Nevada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToElko Context triple: [Lamoille, Nevada, distanceToElko, approximately 20 miles southeast of Elko, Nevada]
-
A.
distanceFromLasVegas
Indicates the measured distance between a given place or object and the city of Las Vegas.
-
B.
distanceFromReno
Indicates the spatial distance between a given entity and the location Reno.
-
C.
distanceFromSaltLakeCity
Indicates the measured distance between a given location and Salt Lake City.
-
D.
distanceToSaltLakeCity
Indicates the measured or calculated distance between a given entity’s location and the city of Salt Lake City.
-
E.
distanceToOgden
Indicates the spatial distance between an entity and the location named Ogden.
- 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_69e2c4d28f848190ac38c400060e943d |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f40db2b5e08190bb55d02a4ceba306 |
completed | May 1, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f2a6d2b20881908dcc3b15cbe3e5b0 |
completed | April 30, 2026, 12:48 a.m. |
| PDg | Predicate description generation | batch_69f40b2f49688190aa1217b7a456dd63 |
completed | May 1, 2026, 2:08 a.m. |
Created at: April 18, 2026, 2:33 a.m.