Triple
T27401962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ridgeland Avenue |
E691871
|
entity |
| Predicate | isSuburbanStreetOf |
P165705
|
FINISHED |
| Object | Chicago |
—
|
NE NERFINISHED |
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: Chicago | Statement: [Ridgeland Avenue, isSuburbanStreetOf, Chicago]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSuburbanStreetOf Context triple: [Ridgeland Avenue, isSuburbanStreetOf, Chicago]
-
A.
isSuburbanRouteOf
Indicates that a given route functions as a suburban segment or service line belonging to, or operating as part of, a larger primary route or network.
-
B.
isSideStreetOf
Indicates that one street is a smaller, less prominent road that connects to or branches off from another main street.
-
C.
isSuburbanNeighborhoodOf
Indicates that one area is a residential neighborhood located within or characteristic of the suburbs of another, typically larger, urban area.
-
D.
isInnerCityRoad
Indicates that a road is located within and primarily serves the inner (central, densely built-up) area of a city.
-
E.
isMinorRoadIn
Indicates that a minor (smaller or less significant) road is located within or forms part of a specified larger area, route, or network.
- F. None of above. chosen
Provenance (4 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f65b14512c8190a40e70319dcc54cd |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
| PDg | Predicate description generation | batch_69f65a6babcc81908052c9907a99c882 |
completed | May 2, 2026, 8:11 p.m. |
Created at: April 27, 2026, 12:29 p.m.