Triple
T32043494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCTE Northern Regional Committee |
E818275
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional committee |
C61423
|
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: regional committee Context triple: [NCTE Northern Regional Committee, instanceOf, regional committee]
-
A.
regional committee of a communist party
A regional committee of a communist party is a territorial governing body responsible for implementing party policies, coordinating local organizations, and directing political, organizational, and ideological work within a specific geographic area.
-
B.
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.
-
C.
regional organisation
A regional organisation is an entity formed by multiple countries or territories within a specific geographic area to coordinate policies, promote cooperation, and address shared economic, political, social, or security issues.
-
D.
UNESCO regional committee
A UNESCO regional committee is a governance body that coordinates, advises, and implements UNESCO’s programs and policies within a specific geographic region, facilitating cooperation among member states and regional partners.
-
E.
regional forum
A regional forum is a structured platform where stakeholders from a specific geographic area gather to discuss, coordinate, and address shared issues, policies, and development priorities.
- F. None of above. chosen
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_69f348fcfb648190859f6be5e04b7cfe |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:19 a.m.