Triple
T24739364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlanta Motor Speedway |
E618507
|
entity |
| Predicate | distanceFromDowntownAtlanta |
P1299
|
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: [Atlanta Motor Speedway, distanceFromDowntownAtlanta, approximately 20 miles south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromDowntownAtlanta Context triple: [Atlanta Motor Speedway, distanceFromDowntownAtlanta, approximately 20 miles south]
-
A.
distanceToAtlanta
Indicates the measured or calculated distance between a given location and the city of Atlanta.
-
B.
distanceFromDowntown
chosen
Indicates the physical distance between a given location and the central downtown area.
-
C.
distanceToColumbusGeorgiaApprox
Indicates an approximate physical distance between a given location and Columbus, Georgia.
-
D.
directionFromAtlanta
Indicates the cardinal or relative compass direction in which one entity is located from Atlanta.
-
E.
distanceToMontgomery
Indicates the spatial distance between a given entity and the location identified as Montgomery.
- 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f497bc12b881908fe3386c66252bf6 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f49366e8d08190adb4b71fe3a14683 |
completed | May 1, 2026, 11:49 a.m. |
Created at: April 18, 2026, 4:04 a.m.