Triple
T9442867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio III Lucania et Bruttii |
E227689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of Italy in the Roman Empire |
C9370
|
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: region of Italy in the Roman Empire Context triple: [Regio III Lucania et Bruttii, instanceOf, region of Italy in the Roman Empire]
-
A.
historical region of Italy
chosen
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.
-
B.
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.
-
C.
province of Italy
A province of Italy is an administrative territorial division within an Italian region that groups together multiple municipalities under a shared local government and jurisdiction.
-
D.
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.
-
E.
Italian state
An Italian state is a historically or politically defined territorial entity on the Italian peninsula, governed by its own institutions and authorities within a specific period or constitutional framework.
- 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_69ca843884488190ad6cbe0153088234 |
completed | March 30, 2026, 2:10 p.m. |
Created at: March 30, 2026, 7:50 p.m.