Triple
T30373191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNCITRAL Working Group VI |
E772606
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United Nations working group |
C15271
|
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: United Nations working group Context triple: [UNCITRAL Working Group VI, instanceOf, United Nations working group]
-
A.
United Nations team
A United Nations team is a group of international professionals collaboratively working under UN mandates to address global issues such as peace, security, development, and human rights.
-
B.
subcommittee of a United Nations committee
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.
United Nations Regional Group
A United Nations Regional Group is a coalition of member states organized by geographic region to coordinate positions, facilitate negotiations, and allocate seats in UN bodies and committees.
-
D.
United Nations specialized agency member grouping
A United Nations specialized agency member grouping is a classification of states or entities organized according to their membership status, participation, or representation within a specific UN specialized agency.
-
E.
intergovernmental working group
chosen
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.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:59 p.m.