Triple

T22028563
Position Surface form Disambiguated ID Type / Status
Subject English ecclesiastical courts E544025 entity
Predicate usedOfficial P24110 FINISHED
Object chancellor 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: chancellor | Statement: [English ecclesiastical courts, usedOfficial, chancellor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedOfficial
Context triple: [English ecclesiastical courts, usedOfficial, chancellor]
  • A. hasOfficialUse chosen
    Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
  • B. isOfficial
    Indicates that an entity holds formal, authorized, or government-recognized status in a given context.
  • C. officialIn
    Indicates that an entity holds an official position, role, or office within a specified organization, institution, or jurisdiction.
  • D. areOfficialIn
    Indicates that an entity holds an official role, position, or capacity within another entity (such as an organization, institution, or jurisdiction).
  • E. usedInOfficialDocumentsOf
    Indicates that something (e.g., a term, symbol, or format) is employed within the formal or legally recognized documents issued by a particular entity 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_69e11e2f98c8819083e11eab90942a78 completed April 16, 2026, 5:36 p.m.
NER Named-entity recognition batch_69f127cdf5c08190ac804664d6e56fe2 completed April 28, 2026, 9:34 p.m.
PD Predicate disambiguation batch_69e6f63b0d048190b241622759aab9de completed April 21, 2026, 3:59 a.m.
Created at: April 16, 2026, 8:24 p.m.