Triple
T31762893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diploma Ottonianum |
E810727
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Holy Roman Empire–papacy treaty |
C27468
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Holy Roman Empire–papacy treaty Context triple: [Diploma Ottonianum, instanceOf, Holy Roman Empire–papacy treaty]
-
A.
Handelsbündnis
Ein Handelsbündnis ist ein Zusammenschluss von Staaten oder Organisationen, der durch Abkommen den gegenseitigen Handel erleichtert, fördert und reguliert.
-
B.
church treaty
chosen
A church treaty is a formal agreement between religious authorities and secular powers that defines the rights, privileges, and obligations of the church within a given political or legal framework.
-
C.
Holy League
The Holy League is a conceptual class representing a coalition of predominantly Catholic states or powers formed to pursue shared religious, political, or military objectives, often in opposition to a common adversary.
-
D.
Byzantine–Sasanian treaty
A Byzantine–Sasanian treaty is a formal diplomatic agreement concluded between the Eastern Roman (Byzantine) Empire and the Sasanian (Sassanid) Persian Empire, typically defining terms of peace, territorial boundaries, tribute, and mutual obligations.
-
E.
Habsburg–Valois conflict
The Habsburg–Valois conflict was a series of 16th-century wars between the Habsburg and Valois dynasties, primarily over control of territories in Italy and Western Europe, that shaped the political balance of early modern Europe.
- F. None of above.
Provenance (1 batch)
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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:31 p.m.