Triple
T20131184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atoka, Tennessee |
E490894
|
entity |
| Predicate | distanceToMemphis |
P70714
|
FINISHED |
| Object | approximately 30 miles north |
—
|
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 north | Statement: [Atoka, Tennessee, distanceToMemphis, approximately 30 miles north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceToMemphis Context triple: [Atoka, Tennessee, distanceToMemphis, approximately 30 miles north]
-
A.
distanceToMemphisApproxMiles
chosen
Indicates an approximate distance, measured in miles, between a given entity’s location and the city of Memphis.
-
B.
distanceToMemphisKm
Indicates the physical distance, measured in kilometers, between a given entity’s location and the city of Memphis.
-
C.
distanceToNashvilleInMilesApprox
Indicates the approximate distance, measured in miles, between a given entity’s location and Nashville.
-
D.
distanceToKnoxville
Indicates the spatial distance between a given entity’s location and the city of Knoxville.
-
E.
distanceToStLouis
Indicates the measured distance between a given entity’s location and the city of St. Louis.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6676183dc8190b65d0def681aaa1e |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:31 p.m.