Triple
T19803377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shelbyville, Kentucky |
E475742
|
entity |
| Predicate | distanceToLouisville |
P35478
|
FINISHED |
| Object | approximately 30 miles east of Louisville |
—
|
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 30 miles east of Louisville | Statement: [Shelbyville, Kentucky, distanceToLouisville, approximately 30 miles east of Louisville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToLouisville Context triple: [Shelbyville, Kentucky, distanceToLouisville, approximately 30 miles east of Louisville]
-
A.
distanceToLouisvilleApprox
chosen
Indicates an approximate distance between a given location and Louisville.
-
B.
distanceToLexington
Indicates the measured or calculated distance between a given entity and the location named Lexington.
-
C.
distanceToIndianapolis
Indicates the measured distance between a given entity’s location and the city of Indianapolis.
-
D.
distanceToStLouis
Indicates the measured distance between a given entity’s location and the city of St. Louis.
-
E.
distanceToPittsburgh
Indicates the spatial distance between a given entity’s location and the city of Pittsburgh.
- F. None of above.
Provenance (3 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_69d8e51bc4208190a1c57d8c5d1b15e4 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654266e18819085698aed8b0e2ba8 |
completed | April 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69e5305858108190bbbfdb9ba3ab9f80 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.