Triple

T360702
Position Surface form Disambiguated ID Type / Status
Subject Lord Privy Seal E7844 entity
Predicate hasCurrentRole P161 FINISHED
Object largely sinecure cabinet office 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: largely sinecure cabinet office | Statement: [Lord Privy Seal, hasCurrentRole, largely sinecure cabinet office]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasCurrentRole
Context triple: [Lord Privy Seal, hasCurrentRole, largely sinecure cabinet office]
  • A. hasRole chosen
    Indicates that an entity occupies, performs, or is assigned a specific role or function in relation to another entity or context.
  • B. hasCurrent
    Indicates that an entity presently possesses, exhibits, or is associated with a particular state, attribute, or resource at the current time.
  • C. hasEquivalentRole
    Indicates that two entities hold roles that are functionally the same or interchangeable in a given context.
  • D. hasAuthorityStatus
    Indicates that one entity holds a particular level or type of official power, control, or decision-making authority over another entity or within a defined context.
  • E. hasAuxiliaryRole
    Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
  • 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_69a2e7e880008190a6ad7e06e5d03007 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ebccb8d88190a31f7c443a0c8566 completed Feb. 28, 2026, 1:21 p.m.
PD Predicate disambiguation batch_69a2e95aeed48190b5e48865cc964938 completed Feb. 28, 2026, 1:10 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.