Triple
T4248901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yellow Springs, Ohio |
E95795
|
entity |
| Predicate | distanceToSpringfield |
P54939
|
FINISHED |
| Object | about 10 miles south of Springfield |
—
|
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 10 miles south of Springfield | Statement: [Yellow Springs, Ohio, distanceToSpringfield, about 10 miles south of Springfield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToSpringfield Context triple: [Yellow Springs, Ohio, distanceToSpringfield, about 10 miles south of Springfield]
-
A.
distanceToBloomington
Indicates the spatial distance between a given entity’s location and the location of Bloomington.
-
B.
distanceToIndianapolis
Indicates the measured distance between a given entity’s location and the city of Indianapolis.
-
C.
distanceToKansasCity
Indicates the spatial distance between a given location or entity and Kansas City.
-
D.
distanceToHartford
Indicates the spatial distance between a given entity’s location and the city of Hartford.
-
E.
distanceToFortCollins
Indicates the spatial distance between a given entity’s location and the city of Fort Collins.
- 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_69b3453f759881909b91f01a1e82c036 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e9df10881908a2f039773f8afaa |
completed | March 12, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69b347f73e008190a908a48ef389945a |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:06 p.m.