Triple

T9313921
Position Surface form Disambiguated ID Type / Status
Subject Minsk Metro E224070 entity
Predicate hasStation P35 FINISHED
Object Mahilyowskaya
Mahilyowskaya is a metro station on the Minsk Metro system in Minsk, Belarus.
E803142 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: Mahilyowskaya | Statement: [Minsk Metro, hasStation, Mahilyowskaya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Mahilyowskaya
Context triple: [Minsk Metro, hasStation, Mahilyowskaya]
  • A. Krasnopresnenskaya
    Krasnopresnenskaya is a Moscow Metro station on the city’s circular Koltsevaya Line, known for its deep-level construction and Soviet-era architectural design.
  • B. Novoslobodskaya
    Novoslobodskaya is a Moscow Metro station famed for its distinctive stained-glass panels and ornate, cathedral-like interior design.
  • C. Khoroshevskaya
    Khoroshevskaya is a Moscow Metro station located on the Big Circle Line, serving the Khoroshyovsky District of the city.
  • D. Rizhskaya
    Rizhskaya is a Moscow Metro station on the Big Circle Line serving the Rizhsky railway terminal area.
  • E. Paveletskaya
    Paveletskaya is a Moscow Metro station named after the nearby Paveletsky railway terminal, serving as a key transport hub in the city’s 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: Mahilyowskaya
Triple: [Minsk Metro, hasStation, Mahilyowskaya]
Generated description
Mahilyowskaya is a metro station on the Minsk Metro system in Minsk, Belarus.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Mahilyowskaya
Target entity description: Mahilyowskaya is a metro station on the Minsk Metro system in Minsk, Belarus.
  • A. Krasnopresnenskaya
    Krasnopresnenskaya is a Moscow Metro station on the city’s circular Koltsevaya Line, known for its deep-level construction and Soviet-era architectural design.
  • B. Novoslobodskaya
    Novoslobodskaya is a Moscow Metro station famed for its distinctive stained-glass panels and ornate, cathedral-like interior design.
  • C. Khoroshevskaya
    Khoroshevskaya is a Moscow Metro station located on the Big Circle Line, serving the Khoroshyovsky District of the city.
  • D. Rizhskaya
    Rizhskaya is a Moscow Metro station on the Big Circle Line serving the Rizhsky railway terminal area.
  • E. Paveletskaya
    Paveletskaya is a Moscow Metro station named after the nearby Paveletsky railway terminal, serving as a key transport hub in the city’s 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_69ca8425f4fc81909c1c586e9a5b7530 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd20b048a081909fd7ec0b6b863063 completed April 1, 2026, 1:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69d139bfc054819084b39c16b7bdb2be completed April 4, 2026, 4:18 p.m.
NEDg Description generation batch_69d13a8e79b081908d5b4dce125df678 completed April 4, 2026, 4:21 p.m.
NED2 Entity disambiguation (via description) batch_69d13b1d2cb481908cdcbeb1a6c81794 completed April 4, 2026, 4:23 p.m.
Created at: March 30, 2026, 7:37 p.m.