Triple
T16968140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vyborgsky District, Saint Petersburg |
E411595
|
entity |
| Predicate | hasMetroStation |
P522
|
FINISHED |
| Object |
Udelnaya station
Udelnaya station is a metro station on the Saint Petersburg Metro serving the Vyborgsky District of the city.
|
E1247476
|
NE FINISHED |
How this triple was built (4 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Udelnaya station | Statement: [Vyborgsky District, Saint Petersburg, hasMetroStation, Udelnaya station]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Udelnaya station Context triple: [Vyborgsky District, Saint Petersburg, hasMetroStation, Udelnaya station]
-
A.
Nikolassee station
Nikolassee station is a Berlin S-Bahn railway station in the Nikolassee district, serving as a local transit hub on the city's southwestern rail network.
-
B.
Letňany station
Letňany station is a Prague Metro station in the Letňany district that serves as the northern terminus of Line C.
-
C.
Frunzenskaya station
Frunzenskaya station is a Moscow Metro station known for its deep-level construction and classic Soviet-era architectural design.
-
D.
Khimvolokno station
Khimvolokno station is a stop on the Volgograd Metrotram light rail system in Volgograd, Russia.
-
E.
Obelya station
Obelya station is a metro station in Sofia, Bulgaria, serving as an interchange point between lines of the Sofia Metro network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Udelnaya station Triple: [Vyborgsky District, Saint Petersburg, hasMetroStation, Udelnaya station]
Generated description
Udelnaya station is a metro station on the Saint Petersburg Metro serving the Vyborgsky District of the city.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Udelnaya station Target entity description: Udelnaya station is a metro station on the Saint Petersburg Metro serving the Vyborgsky District of the city.
-
A.
Nikolassee station
Nikolassee station is a Berlin S-Bahn railway station in the Nikolassee district, serving as a local transit hub on the city's southwestern rail network.
-
B.
Letňany station
Letňany station is a Prague Metro station in the Letňany district that serves as the northern terminus of Line C.
-
C.
Frunzenskaya station
Frunzenskaya station is a Moscow Metro station known for its deep-level construction and classic Soviet-era architectural design.
-
D.
Khimvolokno station
Khimvolokno station is a stop on the Volgograd Metrotram light rail system in Volgograd, Russia.
-
E.
Obelya station
Obelya station is a metro station in Sofia, Bulgaria, serving as an interchange point between lines of the Sofia Metro network.
- F. None of above. chosen
Provenance (5 batches)
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_69d886c9c9d481909afe222093641cae |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d0a6f628819080db47285954729a |
completed | April 18, 2026, 6:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01232d6360819080ac00b8e56f098d |
completed | May 11, 2026, 12:30 a.m. |
| NEDg | Description generation | batch_6a01244a9a1881909a2f0b8394b14cf8 |
completed | May 11, 2026, 12:35 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0124786cc08190881d19c4a1e5a178 |
completed | May 11, 2026, 12:36 a.m. |
Created at: April 10, 2026, 5:31 a.m.