Triple
T32005480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kakhovskaya Line |
E817253
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former line of the Moscow Metro |
C61578
|
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: former line of the Moscow Metro Context triple: [Kakhovskaya Line, instanceOf, former line of the Moscow Metro]
-
A.
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.
-
B.
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.
-
C.
Moscow Metro depot
A Moscow Metro depot is a specialized facility where metro trains are stored, inspected, maintained, and repaired to ensure reliable operation of the Moscow subway system.
-
D.
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.
-
E.
Moscow Monorail station
A Moscow Monorail station is a designated stop along the Moscow Monorail system where passengers can board, alight, and transfer between monorail trains and other modes of public transportation.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:15 a.m.