Triple

T14206034
Position Surface form Disambiguated ID Type / Status
Subject Earl of Cambridge (1362 creation) E352096 entity
Predicate grantedAsRoyalFavor P65823 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: [Earl of Cambridge (1362 creation), grantedAsRoyalFavor, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: grantedAsRoyalFavor
Context triple: [Earl of Cambridge (1362 creation), grantedAsRoyalFavor, yes]
  • A. grantedRoyalPatronageBy
    Indicates that an individual, group, or institution has officially received support, endorsement, or sponsorship from a member of a royal family.
  • B. grantedToEmperor
    Indicates that something (such as a right, title, privilege, or possession) has been formally given or conferred to an emperor.
  • C. royalAppointment chosen
    Indicates a formal position, role, or honor that has been officially granted to an entity by a monarch or royal authority.
  • D. grantedImperialImmediacyBy
    Indicates that an entity received the special legal-political status of imperial immediacy directly from a specified imperial authority.
  • E. royalWarrantGrantedIn
    Indicates that an official royal warrant or authorization was granted in a specified place or jurisdiction.
  • 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_69d827894ac0819097803e57f3227b23 completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de61f84f288190877116330bd54393 completed April 14, 2026, 3:49 p.m.
PD Predicate disambiguation batch_69de05bcd7d48190a4848d9320404aa6 completed April 14, 2026, 9:15 a.m.
Created at: April 10, 2026, 1:05 a.m.