Triple

T33156400
Position Surface form Disambiguated ID Type / Status
Subject King Nicholas VIII E848588 entity
Predicate isInRoyalLineageWith P57937 FINISHED
Object Prince Regent Charles 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: Prince Regent Charles | Statement: [King Nicholas VIII, isInRoyalLineageWith, Prince Regent Charles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isInRoyalLineageWith
Context triple: [King Nicholas VIII, isInRoyalLineageWith, Prince Regent Charles]
  • A. hasRoyalAncestryFrom chosen
    Indicates that one entity possesses royal lineage or descent originating from another entity.
  • B. hasBranchOfImperialFamily
    Indicates that an entity includes or is associated with a specific branch or lineage of an imperial family.
  • C. hasRoyalConnection
    Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
  • D. rankWithinImperialFamily
    Indicates the hierarchical position an individual holds within an imperial family relative to other family members.
  • E. isSecretHeirOf
    Indicates that one person is the undisclosed or hidden rightful heir to another person’s title, position, or inheritance.
  • 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_69f3495b02d08190bb3d366823dffc21 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69f6e02ba6b881908dfafc52d3b75f1c completed May 3, 2026, 5:42 a.m.
PD Predicate disambiguation batch_69f6de09c2f481909f8b2545d3208c9f completed May 3, 2026, 5:32 a.m.
Created at: May 1, 2026, 1:28 a.m.