Triple
T31527716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Independence Avenue (Minsk) |
E804390
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | street in Minsk |
C59280
|
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 Minsk Context triple: [Independence Avenue (Minsk), instanceOf, street in Minsk]
-
A.
street in Minsk
chosen
A street in Minsk is a public urban thoroughfare within the city of Minsk, Belarus, that facilitates vehicular and pedestrian movement while hosting residential, commercial, and cultural infrastructure along its length.
-
B.
Minsk Metro line
A Minsk Metro line is a fixed-route, electrically powered urban rail corridor within the Minsk Metro system, consisting of a sequence of stations and track segments that provide rapid transit service across specific areas of the city.
-
C.
street in Saint Petersburg
A street in Saint Petersburg is a public urban thoroughfare within the city’s historical or modern districts, typically lined with buildings and infrastructure that reflect the architectural, cultural, and social character of Russia’s northern capital.
-
D.
Minsk Metro station
A Minsk Metro station is an underground or surface transit facility within the Minsk Metro system that provides platforms, access points, and passenger services for boarding and alighting metro trains.
-
E.
street in Strasbourg
A street in Strasbourg is a public urban thoroughfare within the city of Strasbourg, typically lined with buildings and infrastructure that support transportation, commerce, and daily life.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 9:59 p.m.