Triple
T10997887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USCM Task Forces |
E259929
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized 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: specialized working group Context triple: [USCM Task Forces, instanceOf, specialized 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.
specialized UN team
A specialized UN team is a focused group of experts assembled by the United Nations to address specific global challenges—such as peacekeeping, humanitarian crises, health emergencies, or technical assistance—through coordinated, mission-driven operations.
-
C.
specialized division
A specialized division is a distinct organizational unit focused on a specific function, expertise, or market segment to improve efficiency and effectiveness within a larger entity.
-
D.
specialist unit
A specialist unit is a dedicated organizational subgroup composed of experts and specialized resources focused on performing specific, complex, or high-priority tasks within a broader system or institution.
-
E.
specialized body of an international organization
A specialized body of an international organization is a distinct, functionally focused entity established within the organization’s framework to carry out specific technical, administrative, or policy-related tasks in support of its overall objectives.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:24 p.m.