Triple

T23293241
Position Surface form Disambiguated ID Type / Status
Subject Boris II of Bulgaria E590090 entity
Predicate associatedDynastyMember P136898 FINISHED
Object Simeon I of Bulgaria 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: Simeon I of Bulgaria | Statement: [Boris II of Bulgaria, associatedDynastyMember, Simeon I of Bulgaria]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: associatedDynastyMember
Context triple: [Boris II of Bulgaria, associatedDynastyMember, Simeon I of Bulgaria]
  • A. associatedWithDynasty
    Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
  • B. refersToPersonWithDynasty
    Indicates that one entity makes reference to a person specifically identified or characterized by their association with a particular dynasty.
  • C. associatedWithDynastyFoundation
    Indicates a relationship in which an entity is connected to the founding or establishment of a particular dynasty.
  • D. associatedWithDynastyOrFaction chosen
    Indicates that an entity is linked to, belongs to, or is significantly connected with a particular dynasty or faction.
  • E. associatedDynasticOrder
    Indicates a relationship where an entity is linked to, or formally connected with, a particular dynastic order.
  • F. None of above.

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_69e25d1af9d88190a0b9b5e8fa608618 completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f196ccd9b481909ab5d3504640025e completed April 29, 2026, 5:27 a.m.
PD Predicate disambiguation batch_69effcf325f88190b320268c3c551abb completed April 28, 2026, 12:18 a.m.
Created at: April 17, 2026, 5:02 p.m.