Triple
T23735630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crownpoint, New Mexico |
E586532
|
entity |
| Predicate | distanceToGallup |
P153464
|
FINISHED |
| Object | about 50 miles northeast of Gallup |
—
|
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: about 50 miles northeast of Gallup | Statement: [Crownpoint, New Mexico, distanceToGallup, about 50 miles northeast of Gallup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToGallup Context triple: [Crownpoint, New Mexico, distanceToGallup, about 50 miles northeast of Gallup]
-
A.
distanceToEureka
Indicates the measured spatial distance between a given entity and the location named Eureka.
-
B.
distanceFromGirvan
Indicates the spatial distance between an entity and the location named Girvan.
-
C.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
D.
distanceToMountRushmore
Indicates the measured or calculated spatial distance between an entity and Mount Rushmore.
-
E.
distanceFromGillam_km
Indicates the distance, measured in kilometers, between an entity and the location Gillam.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad07bd08190b04d7a4c8732a856 |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:10 p.m.