Triple
T3309148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Shore Boulevard West |
E69527
|
entity |
| Predicate | isWaterfrontThoroughfare |
P47954
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Lake Shore Boulevard West, isWaterfrontThoroughfare, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWaterfrontThoroughfare Context triple: [Lake Shore Boulevard West, isWaterfrontThoroughfare, true]
-
A.
isWaterfrontBuilding
Indicates that a building is located directly adjacent to a body of water, such as a river, lake, or ocean.
-
B.
hasWaterfrontArea
Indicates that an entity possesses or includes an area directly adjacent to or bordering a body of water.
-
C.
isUrbanWaterway
Indicates that a waterway is located within, passes through, or primarily serves an urban or metropolitan area.
-
D.
hasWaterfrontDevelopment
Indicates that a location or property includes or is associated with constructed developments directly along or adjacent to a body of water.
-
E.
isInlandWaterwayCommunity
Indicates that a community is located along or associated with an inland waterway, such as a river, canal, or lake, rather than on open coastal waters.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0e9f33c81909cff835a83e0a657 |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada526764881908e4bd52938d5374d |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.