Triple

T6552368
Position Surface form Disambiguated ID Type / Status
Subject Catholic Church hierarchy in the Holy Roman Empire E151158 entity
Predicate hadAllianceWith P600 FINISHED
Object various German princes 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: various German princes | Statement: [Catholic Church hierarchy in the Holy Roman Empire, hadAllianceWith, various German princes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hadAllianceWith
Context triple: [Catholic Church hierarchy in the Holy Roman Empire, hadAllianceWith, various German princes]
  • A. soughtAllianceWith
    Indicates that one entity actively attempted to form an alliance or cooperative partnership with another entity.
  • B. alliance chosen
    Indicates a formal cooperative relationship between entities who agree to support each other in shared goals or interests.
  • C. changesAllianceOf
    Indicates that one entity causes or initiates a change in the alliance or affiliation status of another entity.
  • D. laterAlliesWith
    Indicates that two entities become allies at a later time, after not being allied initially.
  • E. reasonForAlliance
    Indicates that one entity’s motivation, cause, or justification for forming an alliance is based on another specified factor or entity.
  • 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_69c687f3fd60819083bfa583e5bcfa71 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6c1b15d3481908ae66e3d7564b352 completed March 27, 2026, 5:43 p.m.
PD Predicate disambiguation batch_69c6acf6d4148190914b19e9affd8c76 completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:51 p.m.