Triple
T31811997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bezirksamtsleiter von Hamburg-Mitte |
E812033
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | kommunale Leitungsfunktion |
C39901
|
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: kommunale Leitungsfunktion Context triple: [Bezirksamtsleiter von Hamburg-Mitte, instanceOf, kommunale Leitungsfunktion]
-
A.
kommunales politisches Amt
chosen
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.
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.
-
C.
municipal political organization leadership
Municipal political organization leadership encompasses the individuals and structures responsible for guiding, coordinating, and representing a city or town’s political party activities, strategies, and community engagement at the local level.
-
D.
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.
-
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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:44 p.m.