Triple
T6138289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yermo |
E136890
|
entity |
| Predicate | distanceToBarstow |
P53615
|
FINISHED |
| Object | approximately 13 kilometers east |
—
|
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 13 kilometers east | Statement: [Yermo, distanceToBarstow, approximately 13 kilometers east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToBarstow Context triple: [Yermo, distanceToBarstow, approximately 13 kilometers east]
-
A.
distanceFromBarstow
chosen
Indicates the spatial distance between a given location and the reference point of Barstow.
-
B.
distanceFromLasVegas
Indicates the measured distance between a given place or object and the city of Las Vegas.
-
C.
distanceToLosAngeles
Indicates the measured or calculated distance between a given entity’s location and the city of Los Angeles.
-
D.
distanceFromLosAngeles
Indicates the measured or specified distance between a given entity’s location and the city of Los Angeles.
-
E.
distanceToWinnemucca
Indicates the spatial distance between a given entity’s location and the location of Winnemucca.
- F. None of above.
Provenance (3 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_69c008a179388190a3b5a081bbf46d55 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c855a2481909801de9fd55686a4 |
completed | March 22, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c055f19b0c81908be34a00ab218723 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:15 p.m.