Triple

T15543097
Position Surface form Disambiguated ID Type / Status
Subject Petrovskiy E370530 entity
Predicate hasFeminineForm P1613 FINISHED
Object Petrovskaya
Petrovskaya is a Russian feminine surname derived from the masculine form Petrovsky.
E1165922 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: Petrovskaya | Statement: [Petrovskiy, hasFeminineForm, Petrovskaya]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Petrovskaya
Context triple: [Petrovskiy, hasFeminineForm, Petrovskaya]
  • A. Voykovskaya
    Voykovskaya is a Moscow Metro station serving the Zamoskvoretskaya Line in the northern part of the city.
  • B. Piotrovskaya
    Piotrovskaya is the feminine form of the Russian surname Piotrovsky, typically used for women in Russian naming conventions.
  • C. Semyonovskaya
    Semyonovskaya is a station on the Moscow Metro, serving the Sokolnicheskaya Line in the eastern part of Moscow.
  • D. 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.
  • E. Savyolovskaya
    Savyolovskaya is a Moscow Metro station on the Big Circle Line, serving as part of the city’s modern orbital rapid transit 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: Petrovskaya
Triple: [Petrovskiy, hasFeminineForm, Petrovskaya]
Generated description
Petrovskaya is a Russian feminine surname derived from the masculine form Petrovsky.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Petrovskaya
Target entity description: Petrovskaya is a Russian feminine surname derived from the masculine form Petrovsky.
  • A. Voykovskaya
    Voykovskaya is a Moscow Metro station serving the Zamoskvoretskaya Line in the northern part of the city.
  • B. Piotrovskaya
    Piotrovskaya is the feminine form of the Russian surname Piotrovsky, typically used for women in Russian naming conventions.
  • C. Semyonovskaya
    Semyonovskaya is a station on the Moscow Metro, serving the Sokolnicheskaya Line in the eastern part of Moscow.
  • D. 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.
  • E. Savyolovskaya
    Savyolovskaya is a Moscow Metro station on the Big Circle Line, serving as part of the city’s modern orbital rapid transit 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_69d85cc521a08190921fb50319dddc34 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04432c3808190bb5b653bf8de30c6 completed April 16, 2026, 2:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff56bdbca08190b5eb541c5eb4bb09 completed May 9, 2026, 3:46 p.m.
NEDg Description generation batch_69ff577e0ed08190a8f10f9e57c0e967 completed May 9, 2026, 3:49 p.m.
NED2 Entity disambiguation (via description) batch_69ff584b7b28819096fd2fad58ca32d6 completed May 9, 2026, 3:52 p.m.
Created at: April 10, 2026, 4:07 a.m.