Triple

T31980140
Position Surface form Disambiguated ID Type / Status
Subject attempts to repudiate his wife Teutberga E816553 entity
Predicate isChieflyRememberedFor P25528 FINISHED
Object reign of Lothair II of Lotharingia LITERAL 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: reign of Lothair II of Lotharingia | Statement: [attempts to repudiate his wife Teutberga, isChieflyRememberedFor, reign of Lothair II of Lotharingia]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isChieflyRememberedFor
Context triple: [attempts to repudiate his wife Teutberga, isChieflyRememberedFor, reign of Lothair II of Lotharingia]
  • A. knownInHistoryAs
    Indicates that an entity is recognized or referred to by a particular name or title in historical records or accounts.
  • B. fatherNotableFor
    Indicates that a person's father is recognized or distinguished for a particular achievement, role, or characteristic.
  • C. organFamousFor
    Indicates that an organ is widely recognized or notable for a particular characteristic, function, or association.
  • D. celebratedAs
    Indicates that one entity is regarded, honored, or widely recognized as having a particular role, status, or distinction.
  • E. famousForEvent chosen
    Indicates that an entity is widely known or recognized specifically because of a particular event.
  • 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_69f348f6a3008190bfb59ca695fd68e2 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b34a68d48190b596476fe9958cc5 completed May 3, 2026, 2:30 a.m.
PD Predicate disambiguation batch_69f6b151ad008190836c1bcdec503ce2 completed May 3, 2026, 2:22 a.m.
Created at: May 1, 2026, 12:11 a.m.