Triple
T18794169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guangdong Provincial People's Congress |
E459590
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | provincial people's congress |
C125
|
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: provincial people's congress Context triple: [Guangdong Provincial People's Congress, instanceOf, provincial people's congress]
-
A.
district-level people’s committee
A district-level people’s committee is a local executive governing body responsible for implementing laws, policies, and administrative decisions within a specific district under the authority of higher-level state institutions.
-
B.
provincial cabinet
A provincial cabinet is the executive body of a provincial government, composed of the premier and appointed ministers who oversee specific departments and implement provincial policies and laws.
-
C.
subnational legislature
chosen
A subnational legislature is a lawmaking body that operates below the national level—such as a state, provincial, or regional assembly—responsible for creating and overseeing laws and policies within its specific territorial jurisdiction.
-
D.
regional assembly
A regional assembly is a deliberative body composed of representatives from a specific geographic area that debates, formulates, and sometimes enacts policies or regulations affecting that region.
-
E.
province-level administrative division
A province-level administrative division is a primary subnational territorial unit within a country, governed by its own regional authorities under the framework of the national government.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.