Triple

T11229566
Position Surface form Disambiguated ID Type / Status
Subject Severnoye Butovo District E265785 entity
Predicate hasMetroStation P522 FINISHED
Object Skobelevskaya
Skobelevskaya is a Moscow Metro station serving the Severnoye Butovo District in the south of Moscow.
E913923 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: Skobelevskaya | Statement: [Severnoye Butovo District, hasMetroStation, Skobelevskaya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Skobelevskaya
Context triple: [Severnoye Butovo District, hasMetroStation, Skobelevskaya]
  • A. Kuntsevskaya
    Kuntsevskaya is a Moscow Metro station on the Big Circle Line serving the Kuntsevo District in western Moscow.
  • B. Vorontsovskaya
    Vorontsovskaya is a metro station on Moscow’s Big Circle Line serving the southwestern part of the city.
  • C. 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.
  • D. Voykovskaya
    Voykovskaya is a Moscow Metro station serving the Zamoskvoretskaya Line in the northern part of the city.
  • E. Dobryninskaya
    Dobryninskaya is a Moscow Metro station on the circular Koltsevaya Line, known for its Stalinist-era architecture and central location.
  • 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: Skobelevskaya
Triple: [Severnoye Butovo District, hasMetroStation, Skobelevskaya]
Generated description
Skobelevskaya is a Moscow Metro station serving the Severnoye Butovo District in the south of Moscow.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Skobelevskaya
Target entity description: Skobelevskaya is a Moscow Metro station serving the Severnoye Butovo District in the south of Moscow.
  • A. Kuntsevskaya
    Kuntsevskaya is a Moscow Metro station on the Big Circle Line serving the Kuntsevo District in western Moscow.
  • B. Vorontsovskaya
    Vorontsovskaya is a metro station on Moscow’s Big Circle Line serving the southwestern part of the city.
  • C. 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.
  • D. Voykovskaya
    Voykovskaya is a Moscow Metro station serving the Zamoskvoretskaya Line in the northern part of the city.
  • E. Dobryninskaya
    Dobryninskaya is a Moscow Metro station on the circular Koltsevaya Line, known for its Stalinist-era architecture and central location.
  • 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_69d6aac656d48190b275efaa7d6074ee completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e900fbcc8190a3177f8a73564433 completed April 9, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69e4cc4c630c8190a5e43c2108dfb50d completed April 19, 2026, 12:36 p.m.
NEDg Description generation batch_69e4d9e87508819080932fac06fb754d completed April 19, 2026, 1:34 p.m.
NED2 Entity disambiguation (via description) batch_69e4dda28b0081909245b65faae3533b completed April 19, 2026, 1:50 p.m.
Created at: April 8, 2026, 9:30 p.m.