Triple
T31149828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zielonalužskaja line |
E794040
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Minsk Metro line |
C59374
|
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: Minsk Metro line Context triple: [Zielonalužskaja line, instanceOf, Minsk Metro line]
-
A.
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.
-
B.
Saint Petersburg Metro line
A Saint Petersburg Metro line is a distinct rapid transit route within the Saint Petersburg Metro system, consisting of a series of interconnected stations and tracks that provide high-capacity urban rail transport along a defined corridor.
-
C.
Kyiv Metro line
A Kyiv Metro line is a distinct rapid transit route within the Kyiv Metro system, consisting of a sequence of stations and track segments that provide high-capacity, frequent urban rail service along a defined corridor.
-
D.
Moscow Central Diameters line
The Moscow Central Diameters line is a suburban rail transit route in Moscow that operates like an urban through-running commuter line, connecting outlying areas across the city via upgraded existing railway corridors.
-
E.
street in Minsk
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.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:06 p.m.