Triple

T37707868
Position Surface form Disambiguated ID Type / Status
Subject Earldom of Richmond E939240 entity
Predicate extinctAsHereditaryTitle P127257 FINISHED
Object yes 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: yes | Statement: [Earldom of Richmond, extinctAsHereditaryTitle, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: extinctAsHereditaryTitle
Context triple: [Earldom of Richmond, extinctAsHereditaryTitle, yes]
  • A. abolishedAsSovereignTitle
    Indicates that a particular sovereign title or rank has been officially discontinued and no longer exists as a recognized position of rule.
  • B. earldomExtinct chosen
    Indicates that a particular earldom has ceased to exist, typically due to the lack of eligible heirs or formal termination of the title.
  • C. hereditaryTitleInheritance
    Indicates that a hereditary title is passed from one individual to another according to established rules of succession.
  • D. hereditaryTitleFor
    Indicates that one entity is a hereditary title that is held by, or associated with, another entity, typically passed down through a family line.
  • E. extinctDynasty
    Indicates that a dynasty has ceased to exist and no longer continues through ruling descendants or recognized lineage.
  • 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_69f76edb49dc8190b951dce9ce6ef789 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fbaef0cec881908c2742d77d145901 completed May 6, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69fbadf632ec8190b14991c971258307 completed May 6, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:18 p.m.