Triple
T21967838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ulica Powązkowska |
E542504
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | road in Warsaw |
C45592
|
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: road in Warsaw Context triple: [ulica Powązkowska, instanceOf, road in Warsaw]
-
A.
road in Prague
A road in Prague is a public thoroughfare within the city’s urban fabric that supports vehicular and pedestrian movement while reflecting the historical layout, architectural context, and transportation infrastructure of the Czech capital.
-
B.
road in Berlin
A road in Berlin is a public thoroughfare within the city’s urban network that facilitates vehicular, bicycle, and pedestrian movement while integrating with Berlin’s historical layout, public transit, and zoning infrastructure.
-
C.
road in Moscow
A road in Moscow is a transportation route within the city’s urban network that facilitates vehicular and pedestrian movement between various districts, landmarks, and infrastructure.
-
D.
road in Latvia
A road in Latvia is a designated transportation route within the Latvian territory, facilitating vehicular and pedestrian movement between cities, towns, and rural areas according to national infrastructure standards.
-
E.
road in Jakarta
A road in Jakarta is a public transportation corridor within the city’s dense urban network, accommodating mixed traffic—from cars and motorcycles to buses and informal transport—while connecting residential, commercial, and industrial areas amid frequent congestion and diverse street-side activities.
- F. None of above. chosen
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_69e0c47fab1081908dc74a6545dbb051 |
completed | April 16, 2026, 11:14 a.m. |
Created at: April 16, 2026, 8:02 p.m.