Triple

T31311573
Position Surface form Disambiguated ID Type / Status
Subject Kingdom of Neustria E798476 entity
Predicate laterRuledByDynasty P47786 FINISHED
Object Carolingian dynasty 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: Carolingian dynasty | Statement: [Kingdom of Neustria, laterRuledByDynasty, Carolingian dynasty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: laterRuledByDynasty
Context triple: [Kingdom of Neustria, laterRuledByDynasty, Carolingian dynasty]
  • A. establishedUnderDynasty
    Indicates that something (such as an institution, structure, or entity) was founded or created during the rule of a specific dynasty.
  • B. dynastyRuled chosen
    Indicates that a particular dynasty held ruling authority or governance over a specified region, state, or people during a certain period.
  • C. reignInDynasty
    Indicates that a person’s reign or rule occurs within the context of a specific dynasty.
  • D. rulingDynasties
    Indicates that one entity served as the ruling dynasty governing or controlling another entity (such as a state, region, or polity) during a particular historical period.
  • E. dominantDynasty
    Indicates that one dynasty holds prevailing power, influence, or control over a given region or period relative to other dynasties.
  • 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_69f224e1932c81908fef14f7b03a10b7 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69ff397e19a88190a945b826159f5290 completed May 9, 2026, 1:41 p.m.
PD Predicate disambiguation batch_69ff392400d0819088d30d08d4a774bd completed May 9, 2026, 1:39 p.m.
Created at: April 29, 2026, 9:15 p.m.