Triple
T1901220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moesia |
E37692
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient Roman province |
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: ancient Roman province Context triple: [Moesia, instanceOf, ancient Roman province]
-
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.
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.
-
C.
former province of Italy
A former province of Italy is an obsolete administrative division that once functioned as a mid-level local government unit within an Italian region, typically encompassing multiple municipalities before being reorganized or replaced.
-
D.
historical region of Italy
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.
former province of France
A former province of France is a historical territorial and administrative region that existed before the French Revolution, often retaining distinct cultural and regional identities despite no longer having official administrative status.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:35 p.m.