Triple

T14170859
Position Surface form Disambiguated ID Type / Status
Subject Pavlovna E351202 entity
Predicate writtenAs P2203 FINISHED
Object Павловна E351202 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: Павловна | Statement: [Pavlovna, writtenAs, Павловна]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Павловна
Context triple: [Pavlovna, writtenAs, Павловна]
  • A. Pavlovna chosen
    Pavlovna is a Russian patronymic indicating "daughter of Pavel," commonly used as the middle name of women in Russian naming tradition.
  • B. Mikhailovna
    Mikhailovna is a Russian patronymic indicating descent from a father named Mikhail, commonly used as the middle name in female full names.
  • C. Alekseyevna
    Alekseyevna is a Russian patronymic surname suffix meaning "daughter of Alexei," historically borne by women such as Sophia Alekseyevna of Russia.
  • D. Petrovna
    Petrovna is a common Russian patronymic derived from the male given name Pyotr, typically meaning "daughter of Pyotr."
  • E. Nikolaevna
    Nikolaevna is a Russian patronymic indicating "daughter of Nikolai," famously borne by Grand Duchess Anastasia Nikolaevna of Russia.
  • 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_69d8278834a08190b0f1784e58d7b99c completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61b472288190b4a271daa54aa6cd completed April 14, 2026, 3:48 p.m.
NED1 Entity disambiguation (via context triple) batch_69fcf808e6088190a607903be0f2adc7 completed May 7, 2026, 8:37 p.m.
Created at: April 10, 2026, 1:01 a.m.