Triple
T643097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WIPO Coordination Committee |
E16781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | WIPO governing body |
C172
|
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: WIPO governing body Context triple: [WIPO Coordination Committee, instanceOf, WIPO governing body]
-
A.
UN administrative body
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.
-
B.
administrative organ of an international organization
An administrative organ of an international organization is a permanent body responsible for managing the organization’s day-to-day operations, implementing its decisions, and providing support services to its other organs and member states.
-
C.
governing body
chosen
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
D.
WTO mechanism
The WTO mechanism is the institutional framework and set of rules, procedures, and dispute-settlement processes through which the World Trade Organization governs and facilitates international trade among member countries.
-
E.
intergovernmental legal body
An intergovernmental legal body is an organization formed by multiple governments to develop, interpret, or oversee the implementation of international legal norms, agreements, and dispute-resolution mechanisms.
- 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_69a4936be1c88190af56540324b57da7 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:36 p.m.