Triple
T32055726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Conference of Carnuntum |
E818612
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman imperial conference |
C61100
|
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 conference Context triple: [Conference of Carnuntum, instanceOf, Roman imperial conference]
-
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.
imperial forum
An imperial forum is a monumental public complex in ancient Roman cities, commissioned by emperors to serve as a political, religious, and commercial center adorned with grand architecture and statuary.
-
C.
council in Roman Gaul
A council in Roman Gaul was a regional assembly of civic elites and representatives from Gallic cities that met under Roman authority to discuss local affairs, express loyalty to the emperor, and coordinate provincial religious and political activities.
-
D.
ecclesiastical council
An ecclesiastical council is a formal assembly of church leaders convened to deliberate and decide on matters of doctrine, discipline, and church governance.
-
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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:21 a.m.