Triple
T9013746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deutscher Städtetag |
E215542
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | kommunaler Spitzenverband |
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: kommunaler Spitzenverband Context triple: [Deutscher Städtetag, instanceOf, kommunaler Spitzenverband]
-
A.
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.
-
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.
municipal committee of the Chinese Communist Party
A municipal committee of the Chinese Communist Party is the leading local Party organ in a city, responsible for directing political, economic, and social policy implementation in accordance with central Party directives.
-
D.
municipal advisory committee
A municipal advisory committee is a formally appointed group of community members that provides recommendations and expert input to local government officials on specific policy areas, projects, or issues.
-
E.
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.
- 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_69ca83a2bf088190986ee7a8eb90407d |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 7:06 p.m.