Triple

T12526627
Position Surface form Disambiguated ID Type / Status
Subject Princess Aurora Pavlovna Demidova di San Donato E299455 entity
Predicate givenName P17 FINISHED
Object Pavlovna 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: Pavlovna | Statement: [Princess Aurora Pavlovna Demidova di San Donato, givenName, Pavlovna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Pavlovna
Context triple: [Princess Aurora Pavlovna Demidova di San Donato, givenName, Pavlovna]
  • 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. Petrovna
    Petrovna is a common Russian patronymic derived from the male given name Pyotr, typically meaning "daughter of Pyotr."
  • C. Nikolaevna
    Nikolaevna is a Russian patronymic indicating "daughter of Nikolai," famously borne by Grand Duchess Anastasia Nikolaevna of Russia.
  • D. Natalia Petrovna
    Natalia Petrovna was a Russian princess of the Romanov dynasty and sister of Empress Elizabeth of Russia.
  • E. Anna Karlovna
    Anna Karlovna is an alternative name for Anna Leopoldovna, the 18th-century Russian regent who ruled on behalf of the infant Emperor Ivan VI.
  • 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_69d6ada5cdd48190860d9ce30aff69be completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d9545d7e6c819080c3a85c18caa1ae completed April 10, 2026, 7:49 p.m.
NED1 Entity disambiguation (via context triple) batch_69f655762ae88190ab41e23bbd65c566 completed May 2, 2026, 7:50 p.m.
Created at: April 8, 2026, 9:57 p.m.