Triple
T30928242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voltinia |
E787916
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | administrative division of ancient Rome |
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 division of ancient Rome Context triple: [Voltinia, instanceOf, administrative division of ancient Rome]
-
A.
area of ancient Rome
An area of ancient Rome is a distinct geographic or administrative section of the city characterized by specific social, political, religious, or economic functions within the broader urban landscape of Roman civilization.
-
B.
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.
-
C.
Roman administrative district
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.
-
D.
client state of the Roman Empire
A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
-
E.
ancient Roman
An ancient Roman is a person from the civilization of Rome between roughly the 8th century BCE and the 5th century CE, characterized by its distinctive language, culture, politics, and engineering achievements.
- 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_69f224c0b7fc819090cb89df60d23653 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:51 p.m.