Triple

T33481495
Position Surface form Disambiguated ID Type / Status
Subject Prince-Bishop of Osnabrück E857484 entity
Predicate hadImperialImmediateStatus P45698 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: [Prince-Bishop of Osnabrück, hadImperialImmediateStatus, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadImperialImmediateStatus
Context triple: [Prince-Bishop of Osnabrück, hadImperialImmediateStatus, yes]
  • A. hadImperialStatus
    Indicates that an entity possessed or was granted imperial rank, authority, or official status within an empire.
  • B. heldImperialImmediacy chosen
    Indicates that an entity possessed imperial immediacy, meaning it was directly subject to the authority of the emperor rather than to any intermediate feudal lord.
  • C. hadOfficialStatus
    Indicates that an entity possessed a formally recognized or legally sanctioned status within an official system or authority.
  • D. hadSpecialStatusIn
    Indicates that an entity possessed a particular special, exceptional, or non-standard status within a specified context or time period.
  • E. preImperialStatus
    Indicates the status or condition an entity held prior to the establishment or onset of an imperial regime or imperial rule.
  • 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_69f3497472508190b300ebd3fd402367 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6e52fd4bc8190a18d0cd7dad5c6bf completed May 3, 2026, 6:03 a.m.
PD Predicate disambiguation batch_69f6e3da41948190a4cfe866ce184f73 completed May 3, 2026, 5:57 a.m.
Created at: May 1, 2026, 1:38 a.m.