Triple
T35068760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Concilium Galliarum |
E1011807
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman provincial assembly |
C38193
|
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 provincial assembly Context triple: [Concilium Galliarum, instanceOf, Roman provincial assembly]
-
A.
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.
-
B.
council in Roman Gaul
chosen
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.
-
C.
tribune of the plebs
A tribune of the plebs was an elected official in ancient Rome who represented and protected the interests and rights of the common people (plebeians) against the actions of the patrician magistrates and the Senate.
-
D.
regional assembly
A regional assembly is a deliberative body composed of representatives from a specific geographic area that debates, formulates, and sometimes enacts policies or regulations affecting that region.
-
E.
Roman proconsul
A Roman proconsul was a former consul granted extended imperium to govern a province, command armies, and administer justice on behalf of the Roman state.
- 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.