Triple
T15838277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danubian provinces of the Roman Empire |
E384037
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | frontier provinces |
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: frontier provinces Context triple: [Danubian provinces of the Roman Empire, instanceOf, frontier provinces]
-
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.
frontier communities
Frontier communities are small, often isolated settlements located at the edge of established territories, characterized by limited infrastructure, close-knit social ties, and a strong reliance on local resources and self-sufficiency.
-
C.
frontier post
A frontier post is a fortified or administrative outpost located at the edge of a state’s or empire’s territory, serving to monitor, defend, and control movement across its borders.
-
D.
hinterland
The hinterland is the remote or less-developed area lying beyond a city, port, or central region, often economically or socially dependent on that core.
-
E.
proposed province
A proposed province is a geographically defined area formally suggested or envisioned as a new administrative division within a country but not yet legally established or recognized.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:49 a.m.