Triple
T30519564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avenue de Tervueren |
E776657
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Brussels |
C56245
|
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 Brussels Context triple: [Avenue de Tervueren, instanceOf, street in Brussels]
-
A.
road in Belgium
A road in Belgium is a public transportation route, ranging from local streets to major highways, that connects cities, towns, and regions within Belgium and to neighboring countries, following national and European traffic regulations.
-
B.
street in Lyon
A street in Lyon is a public urban thoroughfare within the city of Lyon, France, typically lined with buildings, shops, and residences, and serving as a conduit for pedestrian and vehicular movement as well as local social and commercial activity.
-
C.
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.
-
D.
street in Sofia
A street in Sofia is a public urban thoroughfare within Bulgaria’s capital city, lined with buildings and infrastructure, that facilitates local vehicular and pedestrian movement and connects neighborhoods, services, and landmarks.
-
E.
Count of Brussels
The Count of Brussels is a noble title historically associated with the governance and feudal lordship of the city and surrounding region of Brussels within the medieval Low Countries.
- 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_69f2249b23c4819087fa85496d92f43f |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:17 p.m.