Triple
T38690406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of 382 |
E949245
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman–Gothic treaty |
C60390
|
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: Roman–Gothic treaty Context triple: [Treaty of 382, instanceOf, Roman–Gothic treaty]
-
A.
Roman–barbarian treaty
chosen
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.
-
B.
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.
-
C.
Roman imperial agreement
A Roman imperial agreement is a formal, authoritative accord issued or sanctioned by the emperor that defines obligations, privileges, or arrangements between the imperial government and individuals, groups, or foreign entities within the Roman Empire.
-
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.
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.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:33 p.m.