Triple
T32317510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ager Setinus |
E825680
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman rural district |
C47913
|
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: ancient Roman rural district Context triple: [Ager Setinus, instanceOf, ancient Roman rural district]
-
A.
Roman administrative district
chosen
A Roman administrative district is a territorial unit governed by Roman officials for the purposes of taxation, legal jurisdiction, military organization, and local administration within the Roman state.
-
B.
Roman regio
A Roman regio was an administrative district or region within ancient Rome or its territories, used for organizing governance, census, and urban planning.
-
C.
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.
-
D.
rural province
A rural province is a largely non-urban administrative region characterized by low population density, agricultural or natural-resource-based economies, and small, dispersed communities.
-
E.
Augustan region
The Augustan region is an administrative and geographical subdivision of the Roman Empire established under Emperor Augustus for organizing provincial governance, taxation, and census activities.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:46 a.m.