Triple

T20609983
Position Surface form Disambiguated ID Type / Status
Subject Lord Buckingham E506421 entity
Predicate hasInfluenceSphere P2828 FINISHED
Object royal court 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: royal court | Statement: [Lord Buckingham, hasInfluenceSphere, royal court]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasInfluenceSphere
Context triple: [Lord Buckingham, hasInfluenceSphere, royal court]
  • A. hasInfluenceScope
    Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
  • B. sphereOfInfluence chosen
    Indicates the area or domain within which an entity exerts significant control, impact, or authority over others.
  • C. hasRegionalInfluenceFrom
    Indicates that one entity’s influence, impact, or authority in a region is derived from or shaped by another entity.
  • D. hasSignificantInfluenceIn
    Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
  • E. hasPossibleInfluence
    Indicates that one entity may have an effect on, contribute to, or shape the state, behavior, or outcome of another entity, without asserting that this influence is definite or direct.
  • 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_69e0b4bb2b4081908fa4a72444120f35 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6aad6f53481908fb242947dda7028 completed April 20, 2026, 10:38 p.m.
PD Predicate disambiguation batch_69e5a00c43308190b7ea58d559257e07 completed April 20, 2026, 3:39 a.m.
Created at: April 16, 2026, 11:41 a.m.