Triple
T37439141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regione Siciliana |
E930363
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italian region with special statute |
C65186
|
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: Italian region with special statute Context triple: [Regione Siciliana, instanceOf, Italian region with special statute]
-
A.
province of Italy
A province of Italy is an administrative territorial division within an Italian region that groups together multiple municipalities under a shared local government and jurisdiction.
-
B.
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.
-
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.
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.
-
E.
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.
- F. None of above. chosen
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_69f76ebfdcb8819098562ff3db673b04 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.