Triple
T11008575
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peace of Constance |
E260184
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval peace treaty |
C22138
|
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: medieval peace treaty Context triple: [Peace of Constance, instanceOf, medieval peace treaty]
-
A.
medieval political agreement
A medieval political agreement is a formal or informal pact between rulers, nobles, or institutions that defines mutual obligations—such as protection, allegiance, tribute, or territorial control—within the feudal and dynastic power structures of the Middle Ages.
-
B.
peace settlement
chosen
A peace settlement is a formal agreement between conflicting parties that ends hostilities and establishes terms for lasting resolution and post-conflict relations.
-
C.
peace ordinance
A peace ordinance is a local law or regulation enacted by a governing body to prevent disturbances, maintain public order, and promote peaceful coexistence within a community.
-
D.
church treaty
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.
-
E.
ancient Greek treaty
An ancient Greek treaty is a formal, often inscribed agreement between city-states or powers that establishes terms of peace, alliance, or mutual obligations under the sanction of the gods.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.