Triple
T15795253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vazha-Pshavela metro station |
E382960
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Tbilisi Metro station |
C36503
|
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: Tbilisi Metro station Context triple: [Vazha-Pshavela metro station, instanceOf, Tbilisi Metro station]
-
A.
Volgograd Metrotram station
A Volgograd Metrotram station is a transit facility on the Volgograd Metrotram system that serves as a stop for light rail vehicles, providing passenger access, boarding, and transfers within the city’s hybrid tram–metro network.
-
B.
Moscow Central Circle station
A Moscow Central Circle station is a passenger rail facility on Moscow's orbital urban rail line that provides platforms, services, and access for trains and commuters within the city's integrated transit network.
-
C.
Tehran Metro station
A Tehran Metro station is a designated public transit facility within the Tehran Metro network where passengers can access, board, transfer between, and disembark from metro trains.
-
D.
MARTA rail station
A MARTA rail station is a designated facility along the Metropolitan Atlanta Rapid Transit Authority’s rail network where passengers access, board, and transfer between trains and related transit services.
-
E.
İzmir Metro station
An İzmir Metro station is a designated stop along the İzmir Metro rapid transit system that provides platforms, facilities, and access points for passengers to board, alight, and transfer between metro services within the city of İzmir.
- 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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:48 a.m.