Triple

T17720209
Position Surface form Disambiguated ID Type / Status
Subject Zoloti Vorota E442313 entity
Predicate hasTransferTo P17241 FINISHED
Object Teatralna station 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: Teatralna station | Statement: [Zoloti Vorota, hasTransferTo, Teatralna station]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Teatralna station
Context triple: [Zoloti Vorota, hasTransferTo, Teatralna station]
  • A. Teatralnaya station chosen
    Teatralnaya station is a central Moscow Metro station known for serving the Bolshoi Theatre area and providing key transfers between several metro lines.
  • B. Paulina station
    Paulina station is an elevated Chicago 'L' rapid transit stop in the Lakeview neighborhood, served by the Brown Line.
  • C. Udelnaya station
    Udelnaya station is a metro station on the Saint Petersburg Metro serving the Vyborgsky District of the city.
  • D. Toberín station
    Toberín station is a public transit stop in Bogotá’s TransMilenio bus rapid transit system serving the Toberín neighborhood and surrounding areas.
  • E. Obrera station
    Obrera station is a Mexico City Metro station on Line 8 serving the Obrera neighborhood in the Cuauhtémoc borough.
  • 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_69d8b9ec79688190b86bdcef85a7b3aa completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e4748520a881908dc3446d33236ff7 completed April 19, 2026, 6:21 a.m.
Created at: April 10, 2026, 10:07 a.m.