Triple
T32541260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romans of the Commune of Rome |
E831718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | communal government |
C11461
|
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: communal government Context triple: [Romans of the Commune of Rome, instanceOf, communal government]
-
A.
autonomous community government
An autonomous community government is a regional governing body with constitutionally recognized self-governing powers to manage political, administrative, and fiscal affairs within its territory under a broader national framework.
-
B.
collective municipality
A collective municipality is an administrative unit comprising several smaller municipalities that collaborate to share services and governance functions while retaining their individual local identities.
-
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.
municipal organization
chosen
A municipal organization is a local government entity responsible for providing public services, managing community resources, and implementing policies within a city, town, or other local jurisdiction.
-
E.
municipality
A municipality is a local administrative unit, such as a city, town, or district, governed by elected officials and responsible for providing public services and regulations within its defined geographic area.
- 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_69f34925fd08819084cfe4ec566cb704 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:02 a.m.