Triple
T15470774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CITES Animals Committee |
E376653
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CITES committee |
C12905
|
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: CITES committee Context triple: [CITES Animals Committee, instanceOf, CITES committee]
-
A.
CITES body
chosen
A CITES body is an institutional entity established under the Convention on International Trade in Endangered Species of Wild Fauna and Flora that oversees, regulates, and advises on the international trade of listed species to ensure it does not threaten their survival.
-
B.
CITES scientific advisory body
A CITES scientific advisory body is an expert group that evaluates biological and trade data on listed species to provide science-based recommendations guiding CITES decisions and implementation.
-
C.
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.
-
D.
conference of the parties
A conference of the parties is a formal meeting of all member states to a multilateral agreement, convened to review implementation, negotiate commitments, and make collective decisions under that agreement.
-
E.
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.
- 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_69d85cd21dcc81908646251b1c26ea00 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:33 a.m.