Triple
T23931719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington/Wabash station (CTA) |
E602515
|
entity |
| Predicate | locatedOnLoopSide |
P63544
|
FINISHED |
| Object | east side of 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: east side of Loop | Statement: [Washington/Wabash station (CTA), locatedOnLoopSide, east side of Loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnLoopSide Context triple: [Washington/Wabash station (CTA), locatedOnLoopSide, east side of Loop]
-
A.
locatedOnLoop
Indicates that an entity is situated along or directly on a loop-shaped path, route, or circuit.
-
B.
locationSide
Indicates that one entity is positioned on a particular side (e.g., left, right, front, back) relative to another entity or reference point.
-
C.
isOnLoopSide
chosen
Indicates that one entity is located on the side or segment of a loop structure relative to another reference point or element.
-
D.
locatedAlong
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
E.
situatedOnSideOf
Indicates that one entity is located along or beside the lateral part or edge of another entity.
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf9c223881908e5fa4b5564848e6 |
completed | April 29, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:58 p.m.