Triple

T11461800
Position Surface form Disambiguated ID Type / Status
Subject Natalya Kirillovna Naryshkina E271677 entity
Predicate familyName P18 FINISHED
Object Naryshkina E271677 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: Naryshkina | Statement: [Natalya Kirillovna Naryshkina, familyName, Naryshkina]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Naryshkina
Context triple: [Natalya Kirillovna Naryshkina, familyName, Naryshkina]
  • A. Naryshkina chosen
    Naryshkina is a Russian noble family name historically associated with the boyar clan from which Tsar Alexei I’s second wife, Natalya Naryshkina, and the mother of Peter the Great came.
  • B. Kamarinskaya
    Kamarinskaya is an 1848 orchestral work by Mikhail Glinka, often regarded as a pioneering piece in Russian symphonic music for its use of folk themes.
  • C. Skhodnenskaya
    Skhodnenskaya is a Moscow Metro station on the Tagansko-Krasnopresnenskaya Line serving the northwestern part of the city.
  • D. Kuntsevskaya
    Kuntsevskaya is a Moscow Metro station on the Big Circle Line serving the Kuntsevo District in western Moscow.
  • E. Kolomenskaya
    Kolomenskaya is a Moscow Metro station on the Zamoskvoretskaya Line, serving the Kolomenskoye area in the southern part of 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_69d6aae0c8d881908a5a360c0be3242e completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d822f384f08190b1150ed1389dd31a completed April 9, 2026, 10:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69e5e91f1bb881909a9c36d837e4059b completed April 20, 2026, 8:51 a.m.
Created at: April 8, 2026, 9:35 p.m.