Triple
T28765646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wallace, Kansas |
E726259
|
entity |
| Predicate | distanceToColoradoBorder |
P201959
|
FINISHED |
| Object | approximately 20 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 20 miles | Statement: [Wallace, Kansas, distanceToColoradoBorder, approximately 20 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToColoradoBorder Context triple: [Wallace, Kansas, distanceToColoradoBorder, approximately 20 miles]
-
A.
approxDistanceToColoradoSprings
Indicates that one entity is located at an approximate physical distance from Colorado Springs.
-
B.
distanceFromDenver
Indicates the measured distance between a given location and Denver.
-
C.
distanceToFortCollins
Indicates the spatial distance between a given entity’s location and the city of Fort Collins.
-
D.
distanceToKansasBorder
Indicates the measured spatial distance between a given location and the nearest point on the border of Kansas.
-
E.
distanceToCaliforniaBorder
Indicates the measured or specified distance between a given location and the border of the state of California.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_6a0039c2d5d48190b8ef2c7ef17d8dc5 |
completed | May 10, 2026, 7:54 a.m. |
| PD | Predicate disambiguation | batch_6a0038e525448190a4c815f51595e78d |
completed | May 10, 2026, 7:51 a.m. |
| PDg | Predicate description generation | batch_6a0039c1eec48190963671a5b8c5f631 |
completed | May 10, 2026, 7:54 a.m. |
Created at: April 28, 2026, 6:13 a.m.