Triple

T34123736
Position Surface form Disambiguated ID Type / Status
Subject House of Villiers E875214 entity
Predicate hasRoyalFavourite P196559 FINISHED
Object George Villiers, 1st Duke of Buckingham 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: George Villiers, 1st Duke of Buckingham | Statement: [House of Villiers, hasRoyalFavourite, George Villiers, 1st Duke of Buckingham]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRoyalFavourite
Context triple: [House of Villiers, hasRoyalFavourite, George Villiers, 1st Duke of Buckingham]
  • A. hasRoyalConnection
    Indicates a relationship where an entity is linked or associated in some notable way to royalty, a royal family, or a royal institution.
  • B. hasRoyalHouse
    Indicates that an entity is associated with or belongs to a particular royal house or dynasty.
  • C. hasRoyalStatus
    Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
  • D. hasRoyalArchive
    Indicates that an entity maintains or possesses an official royal archive or collection of records associated with royalty.
  • E. hasRoyalCircle
    Indicates that an entity belongs to, is part of, or is associated with a royal or monarch’s inner circle or court.
  • F. None of above. chosen

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_69f349aa33848190a2e6c5e4533c8444 completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fe5c1a502081909d4024e514309c8e completed May 8, 2026, 9:56 p.m.
PD Predicate disambiguation batch_69fe5a9df21c819087153f5d0bcaa987 completed May 8, 2026, 9:50 p.m.
PDg Predicate description generation batch_69fe5c196f4081908f150d4cd6c528fa completed May 8, 2026, 9:56 p.m.
Created at: May 1, 2026, 1:53 a.m.