Triple
T4025169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Programme, Financial and Administrative Committee |
E91374
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subcommittee |
C10881
|
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: subcommittee Context triple: [Programme, Financial and Administrative Committee, instanceOf, subcommittee]
-
A.
governing body subcommittee
A governing body subcommittee is a smaller, specialized group formed within a larger decision-making organization to focus on specific issues, conduct detailed analysis, and make recommendations or decisions within its defined scope.
-
B.
subcommittee of a United Nations committee
chosen
A subcommittee of a United Nations committee is a smaller, specialized body established under a parent UN committee to focus on specific issues, conduct detailed analysis, and make recommendations to support the committee’s broader mandate.
-
C.
standing committee of a state legislature
A standing committee of a state legislature is a permanent, specialized group of legislators that reviews, amends, and recommends action on proposed laws and issues within a specific policy area.
-
D.
government committee
A government committee is a formally established group of officials or representatives tasked with studying specific issues, developing recommendations, and overseeing particular areas of public policy or administration.
-
E.
selection committee
A selection committee is a group of individuals formally tasked with evaluating candidates or proposals against defined criteria to choose the most suitable options.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:35 p.m.