Triple

T7451180
Position Surface form Disambiguated ID Type / Status
Subject Bishop of Liège E172011 entity
Predicate temporalPower P29191 FINISHED
Object imperial immediacy within the Holy Roman Empire 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: imperial immediacy within the Holy Roman Empire | Statement: [Bishop of Liège, temporalPower, imperial immediacy within the Holy Roman Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: temporalPower
Context triple: [Bishop of Liège, temporalPower, imperial immediacy within the Holy Roman Empire]
  • A. heldTemporalPower chosen
    Indicates that an entity exercised governing or authoritative control over another entity or domain during a specific period of time.
  • B. temporalEffect
    Indicates a relationship where one event, state, or action produces consequences or changes that occur at a later time.
  • C. temporality
    Indicates the time-related relationship between events or states, such as their order, duration, or simultaneity.
  • D. temporalAspect
    Indicates the time-related characteristics or phase (such as duration, frequency, or temporal status) associated with an event or relationship.
  • E. inPowerDuring
    Indicates that an entity holds a position of authority or governance throughout a specified time period.
  • 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_69c68a66554c8190add75c65942c0317 completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f38c28e08190956766a5222fe720 completed March 27, 2026, 9:15 p.m.
PD Predicate disambiguation batch_69c6f039f7248190bb4183f97b605763 completed March 27, 2026, 9:01 p.m.
Created at: March 27, 2026, 3:14 p.m.