Triple
T7014691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sub‑Committee on Structural Reforms |
E162671
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialized working body |
C14681
|
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 body Context triple: [Sub‑Committee on Structural Reforms, instanceOf, specialized working body]
-
A.
specialized body of an international organization
chosen
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.
-
B.
specialized arbitration body
A specialized arbitration body is an independent, expert tribunal established to resolve disputes within a particular field or industry through binding or non-binding arbitral decisions.
-
C.
specialist corps
A specialist corps is a dedicated group of highly trained experts within a larger organization or system, formed to perform complex, technical, or niche tasks that require advanced, domain-specific skills.
-
D.
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.
-
E.
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.
- 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_69c6885a127c8190867b059bdccf13ff |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:34 p.m.