Triple

T4772566
Position Surface form Disambiguated ID Type / Status
Subject Bt E105966 entity
Predicate indicatesHereditaryTitle P1913 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: [Bt, indicatesHereditaryTitle, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: indicatesHereditaryTitle
Context triple: [Bt, indicatesHereditaryTitle, yes]
  • A. hereditaryPeerage chosen
    Indicates that a person holds a noble title that is legally inheritable and passes down through family lineage.
  • B. isRoyalTitle
    Indicates that something is a formal title associated with royalty or a royal rank.
  • C. inheritsTitle
    Indicates that one entity receives and assumes a formal title or rank previously held by another entity, typically through succession or inheritance.
  • D. hasHereditaryChief
    Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
  • E. associatedNobleTitle
    Indicates that an entity is linked to or bears a particular noble or aristocratic title.
  • 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_69bd43f226fc8190b867cc249c2a9042 completed March 20, 2026, 12:56 p.m.
NER Named-entity recognition batch_69bd655f98b0819088c05c5502ecf2cd completed March 20, 2026, 3:18 p.m.
PD Predicate disambiguation batch_69bd6229d8448190a271719e5e30fd82 completed March 20, 2026, 3:05 p.m.
Created at: March 20, 2026, 1:21 p.m.