Triple
T36204816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comune di Concesio |
E1047368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Italian comune administration |
C5933
|
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 comune administration Context triple: [Comune di Concesio, instanceOf, Italian comune administration]
-
A.
Italian comune
chosen
An Italian comune is the basic administrative division in Italy, equivalent to a municipality, responsible for local governance, public services, and community regulations within its defined territory.
-
B.
Italian administrative division
An Italian administrative division is a territorial unit within Italy’s governmental hierarchy, such as a region, province, or municipality, that serves as a level of local governance and public administration.
-
C.
administrative community
An administrative community is a group of individuals and organizations connected through shared governance structures, procedures, and responsibilities for managing and implementing policies or services within a defined domain.
-
D.
medieval commune
A medieval commune was a self-governing urban community in medieval Europe, where townspeople collectively secured legal and political autonomy from feudal lords through charters and communal institutions.
-
E.
commune-level administrative unit
A commune-level administrative unit is the smallest local government division within a country, typically responsible for basic public services, local regulations, and community administration for a town, village, or small group of settlements.
- 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_69f76e414bdc8190996f15a544220a3d |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.