Triple
T29129492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Germania Superior |
E738331
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial frontier province |
C19044
|
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: imperial frontier province Context triple: [Germania Superior, instanceOf, imperial frontier province]
-
A.
frontier province
chosen
A frontier province is a border region of a state or empire where central authority, culture, and control meet and interact with external or less-governed territories, often marked by strategic, economic, and cultural significance.
-
B.
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.
-
C.
Achaemenid province
An Achaemenid province is an administrative region within the Achaemenid Persian Empire, governed by a satrap or local authority responsible for taxation, security, and implementing imperial policies.
-
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.
Roman frontier
The Roman frontier was the shifting boundary zone of the Roman Empire, marked by fortifications, military roads, and garrisoned settlements that controlled movement, trade, and defense between Roman territories and neighboring peoples.
- 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_69f07cb29cdc8190afa55444553de60c |
completed | April 28, 2026, 9:24 a.m. |
Created at: April 28, 2026, 11:30 a.m.