Triple

T17709774
Position Surface form Disambiguated ID Type / Status
Subject Sviatoshynsko–Brovarska line E441531 entity
Predicate hasInterchangeStation P2413 FINISHED
Object Vokzalna NE NERFINISHED

How this triple was built (2 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: Vokzalna | Statement: [Sviatoshynsko–Brovarska line, hasInterchangeStation, Vokzalna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vokzalna
Context triple: [Sviatoshynsko–Brovarska line, hasInterchangeStation, Vokzalna]
  • A. Vokzalna chosen
    Vokzalna is a Kyiv Metro station on the Sviatoshynsko–Brovarska line that serves the city’s main railway terminal.
  • B. Novza station
    Novza station is a metro station on the Tashkent Metro system in Tashkent, Uzbekistan.
  • C. Opatov station
    Opatov station is a Prague Metro station on Line C serving the Opatov district in the southern part of the city.
  • D. Vác
    Vác is a historic town on the Danube in northern Hungary, known for its Baroque architecture and role as a regional cultural and religious center.
  • E. Villach railway junction
    Villach railway junction is a major Austrian rail hub in the city of Villach, serving as a key crossroads for national and international train connections in the state of Carinthia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9ea20b48190ace88bb46b01e6a9 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4729a9a9c81908d65ff0bda12c961 completed April 19, 2026, 6:13 a.m.
Created at: April 10, 2026, 10:05 a.m.