Triple
T7790468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I-285 and I-20 east interchange |
E187363
|
entity |
| Predicate | locationRelativeToCityCenter |
P28261
|
FINISHED |
| Object | east side of Atlanta |
—
|
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: east side of Atlanta | Statement: [I-285 and I-20 east interchange, locationRelativeToCityCenter, east side of Atlanta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeToCityCenter Context triple: [I-285 and I-20 east interchange, locationRelativeToCityCenter, east side of Atlanta]
-
A.
directionFromCityCenter
chosen
Indicates the compass direction in which one location lies relative to the city center.
-
B.
directionFromCityCentre
Indicates the compass direction in which one location lies relative to the city centre.
-
C.
positionOnCityCircle
Indicates that one entity is located along the circular boundary or ring-shaped layout defined by a city.
-
D.
distanceFromCityCenterDirection
Indicates the distance and compass direction of a location relative to the center of a specified city.
-
E.
relativeLocationToCentralPark
Indicates the spatial position or orientation of an entity in relation to Central Park.
- 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_69ca82af2d2c8190963861f5e0b8bf21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cae7ea13f08190a60c5f1863bce816 |
completed | March 30, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69caa48a166c8190a5da0046bde4d9ee |
completed | March 30, 2026, 4:27 p.m. |
Created at: March 30, 2026, 4:25 p.m.