Triple
T36208568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hasheminejad Airport station |
E1047469
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mashhad Metro station |
C63721
|
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: Mashhad Metro station Context triple: [Hasheminejad Airport station, instanceOf, Mashhad Metro station]
-
A.
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.
-
B.
Sofia Metro station
A Sofia Metro station is an underground or surface transit facility within the Sofia Metro system that provides platforms, access points, and related infrastructure for boarding, alighting, and transferring between metro trains.
-
C.
Marmaray station
A Marmaray station is a railway facility serving the Marmaray commuter rail line in Istanbul, providing passenger access to trains that run through the Bosphorus-crossing tunnel and along the city’s intercontinental corridor.
-
D.
Cairo Metro station
A Cairo Metro station is a designated public transit facility within the Cairo Metro network where passengers access, board, and transfer between metro trains and related services.
-
E.
Tbilisi Metro station
A Tbilisi Metro station is an underground or surface transit facility within the Tbilisi Metro system that provides platforms, access points, and passenger services for boarding and alighting metro trains in Tbilisi, Georgia.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.