Triple

T37969281
Position Surface form Disambiguated ID Type / Status
Subject Prince-Bishop of Regensburg E947233 entity
Predicate heldMilitaryAuthority P40117 FINISHED
Object limited territorial forces 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: limited territorial forces | Statement: [Prince-Bishop of Regensburg, heldMilitaryAuthority, limited territorial forces]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heldMilitaryAuthority
Context triple: [Prince-Bishop of Regensburg, heldMilitaryAuthority, limited territorial forces]
  • A. hasMilitaryAuthority chosen
    Indicates that one entity possesses formal power or command to direct, control, or make decisions over the military activities or forces of another entity.
  • B. hadMilitaryPost
    Indicates that an entity held an official position or assignment within a military organization.
  • C. formerMilitaryRole
    Indicates that an entity previously held, but no longer holds, a specific military role or position.
  • D. hasMilitaryStatus
    Indicates that an entity possesses a specific military affiliation, role, or status (such as active duty, reserve, or veteran).
  • E. hadMilitaryFollowing
    Indicates that an entity was supported or backed by a group of military personnel or forces.
  • 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_69f76ef7db908190bba6086673a32300 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fbc7b78f9481909f4f8fc2e3fdcde1 completed May 6, 2026, 10:59 p.m.
PD Predicate disambiguation batch_69fbbd18c9908190928d274f8731dfa8 completed May 6, 2026, 10:13 p.m.
Created at: May 3, 2026, 4:20 p.m.