Triple
T14402708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United Nations Forum on Forests |
E357109
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | UN forest policy body |
C1189
|
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: UN forest policy body Context triple: [United Nations Forum on Forests, instanceOf, UN forest policy body]
-
A.
forestry policy committee
A forestry policy committee is a group of appointed stakeholders and experts responsible for developing, reviewing, and recommending policies that govern the management, conservation, and sustainable use of forest resources.
-
B.
forestry ministry
A forestry ministry is a government department responsible for managing, regulating, and conserving a nation's forest resources and related environmental policies.
-
C.
CITES body
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.
-
D.
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.
-
E.
UN administrative body
chosen
A UN administrative body is an organizational entity within the United Nations responsible for managing, coordinating, and implementing the day-to-day operations, policies, and programs mandated by UN organs and agreements.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:17 a.m.