Triple
T30167327
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio VIII Aemilia |
E766830
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative region of Roman Italy |
C54400
|
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: administrative region of Roman Italy Context triple: [Regio VIII Aemilia, instanceOf, administrative region of Roman Italy]
-
A.
Roman regio
chosen
A Roman regio was an administrative district or region within ancient Rome or its territories, used for organizing governance, census, and urban planning.
-
B.
historical region of Italy
A historical region of Italy is a geographically defined area that played a distinct political, cultural, or administrative role in Italy’s past, often predating or differing from the country’s modern regional boundaries.
-
C.
former province of Italy
A former province of Italy is an obsolete administrative division that once functioned as a mid-level local government unit within an Italian region, typically encompassing multiple municipalities before being reorganized or replaced.
-
D.
Italian administrative division
An Italian administrative division is a territorial unit within Italy’s governmental hierarchy, such as a region, province, or municipality, that serves as a level of local governance and public administration.
-
E.
Roman province
A Roman province is an administrative territory outside the Italian peninsula governed by Rome, overseen by appointed officials, and used for taxation, resource extraction, and military control within the Roman Empire.
- 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_69f2247a968881909d79c18f2bfcb275 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:23 p.m.