Triple

T13900753
Position Surface form Disambiguated ID Type / Status
Subject Imperial Church system E334212 entity
Predicate hasKeyOfficeHolder P16376 FINISHED
Object prince-bishop 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: prince-bishop | Statement: [Imperial Church system, hasKeyOfficeHolder, prince-bishop]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasKeyOfficeHolder
Context triple: [Imperial Church system, hasKeyOfficeHolder, prince-bishop]
  • A. hasOfficeHolderType chosen
    Indicates that an office or position is associated with a specific type or category of office holder (e.g., elected official, appointed official).
  • B. officeHolderIs
    Indicates that one entity serves as the office holder (e.g., official or position occupant) of another entity, such as an office, role, or institution.
  • C. memberHoldsOffice
    Indicates that a member occupies or serves in a specific official position or office within an organization or governing body.
  • D. officeHolderMayBe
    Indicates that a specified person is permitted or eligible to hold a particular office or position.
  • E. officeHolderOf
    Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
  • 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_69d81c5eaa9c819083b1ff8689179565 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de25d9c7a48190ad8fb0ca676f4f7b completed April 14, 2026, 11:32 a.m.
PD Predicate disambiguation batch_69dd464b1ab48190ae50bfc902bf6ef7 completed April 13, 2026, 7:38 p.m.
Created at: April 9, 2026, 10:15 p.m.