Triple
T21500918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee of National Coordinators of GUAM |
E530471
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coordination committee |
C6550
|
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: coordination committee Context triple: [Committee of National Coordinators of GUAM, instanceOf, coordination committee]
-
A.
coordination office
A coordination office is an organizational unit responsible for planning, aligning, and overseeing activities, resources, and communication among different stakeholders to ensure smooth and efficient execution of projects or operations.
-
B.
coordination wiki
A coordination wiki is a collaboratively maintained online space where individuals and groups document plans, resources, and processes to organize, align, and improve collective action toward shared goals.
-
C.
organizational committee
chosen
An organizational committee is a structured group of individuals formally appointed within an organization to plan, coordinate, and oversee specific functions, projects, or decision-making processes.
-
D.
interagency committee
An interagency committee is a collaborative body composed of representatives from multiple government agencies formed to coordinate policies, share information, and address cross-cutting issues.
-
E.
Economic Coordination Committee of the Cabinet
The Economic Coordination Committee of the Cabinet is a high-level governmental body responsible for formulating, coordinating, and approving key economic and financial policies and decisions on behalf of the federal cabinet.
- 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_69e0c45bd15481909fba5910765cdda2 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:24 p.m.