Triple

T17900914
Position Surface form Disambiguated ID Type / Status
Subject Tsaritsa Irina E447573 entity
Predicate portrayedAlongside P14987 FINISHED
Object Desislava NE NERFINISHED

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: Desislava | Statement: [Tsaritsa Irina, portrayedAlongside, Desislava]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Desislava
Context triple: [Tsaritsa Irina, portrayedAlongside, Desislava]
  • A. Dessislava chosen
    Dessislava was a medieval Bulgarian noblewoman and patron associated with the commissioning and decoration of the Boyana Church near Sofia.
  • B. Dimitrova
    Dimitrova is a common Bulgarian feminine surname derived from the masculine form Dimitrov.
  • C. Pavlina
    Pavlina is a feminine given name, commonly used in Slavic countries as a variant of names like Paulina.
  • D. Vladimira
    Vladimira is a feminine given name, primarily used in Slavic cultures, derived from the male name Vladimir.
  • E. Sveta
    Sveta is a common Russian diminutive form of the female given name Svetlana, often used as an affectionate or informal nickname.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f59bd48190a6fc925a855b8bac completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e49d8321bc8190a3f679d96323cbbb completed April 19, 2026, 9:16 a.m.
Created at: April 10, 2026, 10:19 a.m.