Triple
T28410325
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Germania |
E719645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Roman provincial region |
C5440
|
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: Roman provincial region Context triple: [Roman Germania, instanceOf, Roman provincial region]
-
A.
Roman province
chosen
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 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.
-
C.
regio of Rome under Augustus
A regio of Rome under Augustus was one of the fourteen administrative districts into which the emperor reorganized the city for more efficient governance, public order, and urban management.
-
D.
Sasanian province
A Sasanian province was an administrative territorial unit of the Sasanian Empire, governed by appointed officials responsible for taxation, justice, and military organization within its boundaries.
-
E.
province of the Byzantine Empire
A province of the Byzantine Empire was an administrative and territorial unit governed by imperial officials, responsible for local civil, military, and fiscal management under the authority of the central Byzantine state.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:26 a.m.