Triple
T33283507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treaty of Serdica |
E852115
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman imperial agreement |
C61436
|
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 imperial agreement Context triple: [Treaty of Serdica, instanceOf, Roman imperial agreement]
-
A.
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.
-
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 conference
A Roman imperial conference is a formal gathering convened by the emperor to deliberate on matters of state, policy, military strategy, or administration with high-ranking officials and advisors.
-
D.
Roman political alliance
A Roman political alliance is a formal or informal partnership between individuals, factions, or states in ancient Rome formed to consolidate power, advance mutual political interests, and influence governance and decision-making.
-
E.
Roman imperial policy
Roman imperial policy refers to the strategies, laws, and administrative practices employed by Roman emperors to maintain control, integrate diverse provinces, manage resources, and project power across the empire.
- F. None of above. chosen
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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:32 a.m.