Triple
T29450647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chinese Communist Party Jingmen Municipal Committee |
E746965
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | local ruling party authority |
C1677
|
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: local ruling party authority Context triple: [Chinese Communist Party Jingmen Municipal Committee, instanceOf, local ruling party authority]
-
A.
local soviet authority
A local soviet authority is a governing body at the city, district, or regional level in the Soviet system, composed of elected deputies who administer local affairs under the centralized control of higher soviet organs and the Communist Party.
-
B.
one‑party state authority
chosen
A one-party state authority is a governing body in which a single political party monopolizes political power, controls state institutions, and suppresses or severely restricts opposition.
-
C.
provincial authority
A provincial authority is a regional governing body responsible for administering laws, policies, and public services within a specific province under a broader national framework.
-
D.
local organ of state power
A local organ of state power is a governmental body operating at the subnational level that exercises state authority and administers public affairs within a defined local territory in accordance with national law.
-
E.
local government politics
Local government politics encompasses the processes, power dynamics, and decision-making activities through which local officials, institutions, and community stakeholders shape policies and allocate resources within municipalities or regions.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 3:32 p.m.