Triple

T36750326
Position Surface form Disambiguated ID Type / Status
Subject Andronikos E907891 entity
Predicate notableDynastyAssociation P7426 FINISHED
Object Palaiologos dynasty E38020 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: Palaiologos dynasty | Statement: [Andronikos, notableDynastyAssociation, Palaiologos dynasty]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: notableDynastyAssociation
Context triple: [Andronikos, notableDynastyAssociation, Palaiologos dynasty]
  • A. notableDynastyGeneration
    Indicates that one dynasty generation is notably significant or distinguished in relation to another within a historical or genealogical context.
  • B. prominentDynasty
    Indicates that a dynasty holds significant historical, political, or cultural importance relative to other dynasties.
  • C. associatedWithDynasty chosen
    Indicates that an entity has a historical, political, cultural, or familial connection to a specific dynasty.
  • D. notableDynastyInSouth
    Indicates that a dynasty is recognized as historically significant and is located in or primarily associated with the southern region of a given geographic or political context.
  • E. dynastyAlsoKnownAs
    Indicates that a dynasty is referred to by an alternative name, alias, or variant designation.
  • F. None of above.

Provenance (4 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_69f76e76d10881909ec1679bc043108c completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_6a037c8e2c648190a65fc9c7872861af completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a3c173778e48190b12646065ec95ade completed June 24, 2026, 5:43 p.m.
PD Predicate disambiguation batch_6a037a0e039481908a4a2666f76c5363 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:12 p.m.