Triple
T28883356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springer, New Mexico |
E732481
|
entity |
| Predicate | distanceToRaton |
P202082
|
FINISHED |
| Object | approximately 40 miles south |
—
|
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 40 miles south | Statement: [Springer, New Mexico, distanceToRaton, approximately 40 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToRaton Context triple: [Springer, New Mexico, distanceToRaton, approximately 40 miles south]
-
A.
distanceToSneek
Indicates the spatial distance between an entity and the location named Sneek.
-
B.
distanceFromGoal
Indicates the measured or estimated separation between an entity’s current position and its intended goal or target state.
-
C.
distanceFromBol
Indicates the measured distance between an entity and a specified beginning-of-line (BOL) reference point.
-
D.
distanceFromCentre
Indicates the measured or specified distance of an entity from a defined central point.
-
E.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
- 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_69f05b07bdec819080cadfe147aa1f25 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a004d0b46148190bcec4ea67acfe170 |
completed | May 10, 2026, 9:16 a.m. |
| PD | Predicate disambiguation | batch_6a004c92283081909f229c1720af155a |
completed | May 10, 2026, 9:14 a.m. |
| PDg | Predicate description generation | batch_6a004d0a95548190ac822cd1d54edf42 |
completed | May 10, 2026, 9:16 a.m. |
Created at: April 28, 2026, 7:47 a.m.