Triple
T30286770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grafton Street |
E770259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Dublin |
C22828
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: street in Dublin Context triple: [Grafton Street, instanceOf, street in Dublin]
-
A.
road in Ireland
chosen
A road in Ireland is a public thoroughfare, ranging from narrow rural lanes to major motorways, that connects towns, cities, and regions across the Irish landscape and is classified and maintained according to national and local transport standards.
-
B.
bridge over the River Liffey
A bridge over the River Liffey is a structural crossing that spans the river in Dublin, connecting different parts of the city for pedestrians, vehicles, or public transport.
-
C.
street in Reykjavík
A street in Reykjavík is a public urban thoroughfare within Iceland’s capital city, typically lined with a mix of colorful buildings, local businesses, and pedestrian-friendly infrastructure shaped by the city’s Nordic climate and culture.
-
D.
street in Melbourne
A street in Melbourne is a public urban thoroughfare within the city’s grid or suburban layout, lined with a mix of residential, commercial, and cultural buildings, and shaped by the city’s distinctive tram network, laneways, and diverse neighborhoods.
-
E.
street in Lisbon
A street in Lisbon is a public urban thoroughfare, often narrow and winding, lined with historic buildings, tiled facades, and calçada portuguesa pavements that connect neighborhoods and support pedestrian and vehicular movement.
- F. None of above.
Provenance (1 batch)
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_69f224875c288190a9b96b975006ec4a |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:46 p.m.