Triple
T1973166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio VIII Forum Romanum |
E42846
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regio of Rome |
C9381
|
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: regio of Rome Context triple: [Regio VIII Forum Romanum, instanceOf, regio of Rome]
-
A.
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.
-
B.
Roman town
A Roman town is an urban settlement in the Roman Empire characterized by planned streets, public buildings such as forums, baths, and temples, and a structured social and administrative organization under Roman law and culture.
-
C.
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.
-
D.
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.
-
E.
metropolitan city of Italy
A metropolitan city of Italy is a large urban area and its surrounding municipalities governed as a single administrative entity with special powers for planning, infrastructure, and local services.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:36 p.m.