Triple
T37398982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Federal Charter of 1291 |
E928938
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval alliance treaty |
C13699
|
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 alliance treaty Context triple: [Federal Charter of 1291, instanceOf, medieval alliance 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.
Roman–barbarian treaty
A Roman–barbarian treaty is a formal agreement between the Roman state and a non-Roman tribal group that defines terms of peace, alliance, military service, territorial rights, and mutual obligations.
-
C.
treaty-based alliance
chosen
A treaty-based alliance is a formal agreement between two or more sovereign entities that legally binds them to cooperate on specified political, military, economic, or other mutual interests under defined terms and obligations.
-
D.
historical alliance
A historical alliance is a formal or informal partnership between states, groups, or leaders formed in the past to pursue shared political, military, economic, or cultural goals.
-
E.
Handelsbündnis
Ein Handelsbündnis ist ein Zusammenschluss von Staaten oder Organisationen, der durch Abkommen den gegenseitigen Handel erleichtert, fördert und reguliert.
- 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_69f76ebbf79c8190b85bbcf3a6be57e4 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.