Triple
T18559062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 79th Street (Chicago) |
E453582
|
entity |
| Predicate | orientationRelativeToDowntown |
P28261
|
FINISHED |
| Object | south of Chicago Loop |
—
|
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: south of Chicago Loop | Statement: [79th Street (Chicago), orientationRelativeToDowntown, south of Chicago Loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orientationRelativeToDowntown Context triple: [79th Street (Chicago), orientationRelativeToDowntown, south of Chicago Loop]
-
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.
distanceFromCityCenterDirection
Indicates the distance and compass direction of a location relative to the center of a specified city.
-
D.
isDowntownEndpointOf
Indicates that a location serves as the downtown terminus or endpoint of a route, line, or path.
-
E.
latitudeDirection
Indicates the cardinal direction (north or south) associated with a given latitude value relative to the equator.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53808c3fc8190aac38b29296cee13 |
completed | April 19, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:41 a.m.