Triple
T27633990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kommunalverfassung von Groß-Berlin |
E696422
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Kommunalverfassung |
C8884
|
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: Kommunalverfassung Context triple: [Kommunalverfassung von Groß-Berlin, instanceOf, Kommunalverfassung]
-
A.
kommunales politisches Amt
Ein kommunales politisches Amt ist eine öffentliche Funktion innerhalb einer Gemeinde oder Stadt, in der gewählte oder ernannte Personen politische Entscheidungen für die lokale Gemeinschaft treffen und verwalten.
-
B.
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.
-
C.
system of local government
chosen
A system of local government is an organized framework of institutions, powers, and processes through which local authorities manage public services, enforce regulations, and represent community interests within a defined geographic area.
-
D.
municipal administration
Municipal administration is the organizational structure and processes through which a local government manages public services, implements policies, and oversees the day-to-day operations of a municipality.
-
E.
municipal organization
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.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 2:22 p.m.