Triple
T8723868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNSO Working Groups |
E207081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | policy development working group |
C17702
|
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: policy development working group Context triple: [GNSO Working Groups, instanceOf, policy development working group]
-
A.
collaborative working group
chosen
A collaborative working group is a coordinated team of individuals who share responsibilities, knowledge, and decision-making to achieve a common goal or complete a specific project.
-
B.
intergovernmental working group framework
An intergovernmental working group framework is a structured, collaborative arrangement through which multiple governments coordinate, negotiate, and develop joint policies, standards, or actions on shared issues.
-
C.
policy analysis unit
A policy analysis unit is an organizational entity responsible for systematically evaluating, comparing, and forecasting the impacts of public or institutional policies to inform evidence-based decision-making.
-
D.
intergovernmental working group
An intergovernmental working group is a collaborative body composed of representatives from multiple governments tasked with developing, coordinating, or advising on policies, standards, or actions in a specific issue area.
-
E.
policy program
A policy program is a coordinated set of government or organizational initiatives, actions, and resources designed to achieve specific public or institutional goals through the implementation of formal policies.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.