Triple
T22147363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INTOSAI Capacity Building Committee |
E547321
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized committee of INTOSAI |
C30665
|
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: specialized committee of INTOSAI Context triple: [INTOSAI Capacity Building Committee, instanceOf, specialized committee of INTOSAI]
-
A.
Specialized committee
chosen
A specialized committee is a focused group of individuals formed within a larger organization to address, investigate, or manage specific issues, tasks, or areas of expertise.
-
B.
UNESCO intergovernmental committee
The UNESCO intergovernmental committee is a decision-making body composed of representatives from member states that oversees the implementation of UNESCO conventions, programs, and policies through intergovernmental cooperation and dialogue.
-
C.
international financial institution committee
A formal group within or across international financial institutions that coordinates policies, oversight, and decision-making on global financial, monetary, or development issues among member states or organizations.
-
D.
international expert committee
An international expert committee is a formally organized group of specialists from multiple countries who collaboratively provide authoritative analysis, guidance, and recommendations on complex global issues within a specific domain.
-
E.
international committee
An international committee is a formally organized group of representatives from multiple countries who collaborate to discuss, coordinate, and make decisions on issues of shared global concern.
- 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_69e11e3b52088190ad5df386d01eb2fb |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:33 p.m.