Triple

T2223447
Position Surface form Disambiguated ID Type / Status
Subject Bolshaya Koltsevaya Line E48192 entity
Predicate hasStation P35 FINISHED
Object Lefortovo E218144 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: Lefortovo | Statement: [Bolshaya Koltsevaya Line, hasStation, Lefortovo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lefortovo
Context triple: [Bolshaya Koltsevaya Line, hasStation, Lefortovo]
  • A. Lefortovo chosen
    Lefortovo is a Moscow Metro station on the Big Circle Line serving the historic Lefortovo district of Russia’s capital.
  • B. Perovo
    Perovo is a Moscow Metro station serving the Kalininsko–Solntsevskaya Line in the Perovo District of eastern Moscow.
  • C. Karlov
    Karlov is a historic university campus complex in Prague that houses several faculties of Charles University, particularly in the medical and natural sciences.
  • D. Metelkova City
    Metelkova City is an autonomous cultural and social center in Ljubljana, Slovenia, known for its alternative art scene, vibrant nightlife, and politically engaged community.
  • E. Lübars
    Lübars is a historic, village-like district in Berlin’s Reinickendorf borough, known for its rural character, fields, and preserved traditional architecture within the city.
  • 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_69a88aa1ee708190862c8c378c41e9eb completed March 4, 2026, 7:40 p.m.
NER Named-entity recognition batch_69abc03d1df88190950c691a4c246bd1 completed March 7, 2026, 6:05 a.m.
NED1 Entity disambiguation (via context triple) batch_69ae6562c9448190b53c068c900bf0bf completed March 9, 2026, 6:14 a.m.
Created at: March 4, 2026, 7:47 p.m.