Triple
T16451865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio IV Samnium |
E399571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of Italy (Roman Empire) |
C27363
|
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 (Roman Empire) Context triple: [Regio IV Samnium, instanceOf, region of Italy (Roman Empire)]
-
A.
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.
-
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.
core territory of the Roman Empire
The core territory of the Roman Empire comprises the Italian peninsula and the western-central Mediterranean heartlands that formed the political, economic, and cultural center of Roman power and administration.
-
D.
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.
-
E.
part of the Roman Empire
chosen
A "part of the Roman Empire" is any geographically or administratively defined region, province, or territory that was under the political control and governance of the Roman state during its historical existence.
- 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_69d87f2c6778819080fcfae53be8f12a |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:10 a.m.