Triple
T4739891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Shore Drive |
E105212
|
entity |
| Predicate | isUrbanHighway |
P28220
|
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 Drive, isUrbanHighway, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isUrbanHighway Context triple: [Lake Shore Drive, isUrbanHighway, true]
-
A.
isUrbanFreeway
chosen
Indicates that a roadway segment functions as a high-capacity, limited-access freeway located within an urban area.
-
B.
isUrbanRoute
Indicates that a route is located within, passes through, or primarily serves an urban or metropolitan area.
-
C.
isUrbanDistrict
Indicates that a given district is classified as an urban administrative or residential area rather than a rural one.
-
D.
isUrbanNeighborhood
Indicates that a given area functions as a neighborhood located within an urban or city environment.
-
E.
isUrbanized
Indicates that a place or area has been developed with dense human settlement, infrastructure, and built environment characteristic of a city or town.
- 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_69bd43ef87a48190a5bc3600711aa032 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6486f8608190908e43b777810c44 |
completed | March 20, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69bd6221c3b881908604f35f8de6f16b |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:19 p.m.