Triple
T21997030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | INTOSAI Knowledge Sharing and Knowledge Services Committee |
E543232
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | INTOSAI committee |
C12193
|
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: INTOSAI committee Context triple: [INTOSAI Knowledge Sharing and Knowledge Services Committee, instanceOf, INTOSAI committee]
-
A.
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.
-
B.
international committee
chosen
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.
-
C.
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.
-
D.
BIS committee
A BIS committee is a formal group within the Bureau of Indian Standards responsible for developing, reviewing, and maintaining national standards in a specific technical or sectoral domain.
-
E.
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.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:19 p.m.