Triple
T3691117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebei–Chahar political and military affairs |
E78344
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political administrative structure |
C4277
|
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: political administrative structure Context triple: [Hebei–Chahar political and military affairs, instanceOf, political administrative structure]
-
A.
public administration
Public administration is the field and practice of implementing government policies, managing public programs, and coordinating resources and personnel to serve the public interest and promote effective governance.
-
B.
political institutions
chosen
Political institutions are the formal and informal structures, rules, and organizations that shape how political power is acquired, exercised, and constrained within a society.
-
C.
political entity
A political entity is an organized group or jurisdiction, such as a state, nation, or governing body, that holds authority to make and enforce collective decisions over a defined population and territory.
-
D.
state administration
State administration is the organized system of public institutions and officials responsible for implementing government policies, managing public services, and enforcing laws within a state's territory.
-
E.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
- 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_69ad85e285a081908f8cbfa9e2ed9b75 |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:26 p.m.