Triple
T15101610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parma and Piacenza ducal domain |
E360679
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | early modern Italian state |
C2530
|
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: early modern Italian state Context triple: [Parma and Piacenza ducal domain, instanceOf, early modern Italian state]
-
A.
early modern state
chosen
An early modern state is a centralized political entity that emerged in Europe between the 15th and 18th centuries, characterized by growing bureaucratic administration, territorial sovereignty, standing armies, and increasingly standardized systems of law and taxation.
-
B.
Italian city-state
An Italian city-state is an independent, self-governing urban center and its surrounding territory on the Italian peninsula, typically flourishing in the medieval and Renaissance periods through commerce, politics, and culture.
-
C.
maritime republic
A maritime republic is a city-state or polity whose power, wealth, and political institutions are primarily based on seaborne trade, naval strength, and control of maritime routes.
-
D.
Italian state
An Italian state is a historically or politically defined territorial entity on the Italian peninsula, governed by its own institutions and authorities within a specific period or constitutional framework.
-
E.
early modern polity
An early modern polity is a territorially bounded, politically organized community between roughly 1500 and 1800 that exercised authority through evolving institutions of governance, law, and sovereignty amid processes of state formation and imperial expansion.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:05 a.m.