Triple
T37586589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decatur, Indiana |
E935129
|
entity |
| Predicate | distanceToFortWayne |
P205995
|
FINISHED |
| Object | approximately 20 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 20 miles south | Statement: [Decatur, Indiana, distanceToFortWayne, approximately 20 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToFortWayne Context triple: [Decatur, Indiana, distanceToFortWayne, approximately 20 miles south]
-
A.
distanceToIndianapolis
Indicates the measured distance between a given entity’s location and the city of Indianapolis.
-
B.
distanceToMadison
Indicates the spatial distance between a given entity and the location identified as Madison.
-
C.
distanceToSouthBend
Indicates the measured or calculated distance between a given entity and the location South Bend.
-
D.
distanceToDetroit
Indicates the measured or calculated spatial distance between a given entity and the location of Detroit.
-
E.
distanceFromCincinnati
Indicates the measured distance between a given location and the city of Cincinnati.
- 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_69f76ece61dc8190a0ab33f8d87d0a7e |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:17 p.m.