Triple

T1946750
Position Surface form Disambiguated ID Type / Status
Subject Sokolnicheskaya Line E42070 entity
Predicate hasStation P35 FINISHED
Object Kommunarka station E222351 NE FINISHED

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: Kommunarka station | Statement: [Sokolnicheskaya Line, hasStation, Kommunarka station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kommunarka station
Context triple: [Sokolnicheskaya Line, hasStation, Kommunarka station]
  • A. Kommunarka station chosen
    Kommunarka station is a southern terminal metro station on Moscow’s Sokolnicheskaya Line, serving the rapidly developing Kommunarka district.
  • B. People’s Square Station
    People’s Square Station is a major Shanghai Metro interchange hub located beneath People’s Square in central Shanghai, China.
  • C. Traktorozavodskaya station
    Traktorozavodskaya station is a stop on Volgograd’s Metrotram system serving the industrial Traktorozavodsky district of the city.
  • D. Komsomolskaya station
    Komsomolskaya station is a stop on the Volgograd Metrotram light rail system in Volgograd, Russia.
  • E. Lichtenberg station
    Lichtenberg station is a major railway and transport hub in the Lichtenberg district of Berlin, Germany, serving regional, long-distance, and urban transit lines.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69a8870e08fc8190a319cbf2600db15f completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb32ebae881908f7541301f0198ae completed March 7, 2026, 5:10 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae1fd173b881909fbd454fc9d7fabb completed March 9, 2026, 1:18 a.m.
Created at: March 4, 2026, 7:36 p.m.