Triple
T34490128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dexter, New Mexico |
E885443
|
entity |
| Predicate | distanceToRoswell |
P205444
|
FINISHED |
| Object | approximately 18 miles |
—
|
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 18 miles | Statement: [Dexter, New Mexico, distanceToRoswell, approximately 18 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToRoswell Context triple: [Dexter, New Mexico, distanceToRoswell, approximately 18 miles]
-
A.
distanceFromAlamogordo
Indicates the spatial distance between a given entity and the location of Alamogordo.
-
B.
positionOnRoswell
Indicates that one entity occupies a specific position or location relative to the Roswell reference (e.g., a map, route, or coordinate system associated with Roswell).
-
C.
distanceToClovis
Indicates the spatial distance between a given entity and the reference location Clovis.
-
D.
directionFromRoswell
Indicates the cardinal or relative compass direction of one place or object as measured from Roswell.
-
E.
distanceFromSocorro
Indicates the spatial distance between an entity and the reference location Socorro.
- 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_69f349cafcec8190997b45b3fdc16c27 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c92f03c8190ae2751270b195423 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c80ba448190853011097a151b7e |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 2:01 a.m.