Triple

T17264254
Position Surface form Disambiguated ID Type / Status
Subject Prince-bishop of Cologne E419083 entity
Predicate positionHeldInImperialDiet P44656 FINISHED
Object ecclesiastical prince-elector 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: ecclesiastical prince-elector | Statement: [Prince-bishop of Cologne, positionHeldInImperialDiet, ecclesiastical prince-elector]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: positionHeldInImperialDiet
Context triple: [Prince-bishop of Cologne, positionHeldInImperialDiet, ecclesiastical prince-elector]
  • A. hasPositionInImperialDiet chosen
    Indicates that an entity holds or held a formal seat or role within the Imperial Diet.
  • B. hadParliamentaryRepresentationIn
    Indicates that an entity was represented by one or more members in a specified parliament or legislative body during a given time or period.
  • C. positionHeldInTheLegislativeBody
    Indicates that an entity holds or has held a specific official role or seat within a legislative body.
  • D. rankInParliament
    Indicates the hierarchical position or level of authority that an individual holds within a parliamentary body.
  • E. hadMemberInImperialFamily
    Indicates that an entity had at least one member belonging to an imperial family.
  • 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_69d886d9ab108190b70edd8d17aa1204 completed April 10, 2026, 5:12 a.m.
NER Named-entity recognition batch_69e42f4432fc81908fd90865822af1fa completed April 19, 2026, 1:26 a.m.
PD Predicate disambiguation batch_69e3832a284481908a8a3da7ac91de5a completed April 18, 2026, 1:12 p.m.
Created at: April 10, 2026, 5:40 a.m.