Triple
T8495667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multilateral System of Access and Benefit-sharing |
E201092
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multilateral system |
C3195
|
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: multilateral system Context triple: [Multilateral System of Access and Benefit-sharing, instanceOf, multilateral system]
-
A.
treaty system
chosen
A treaty system is a structured network of formal agreements between states or entities that collectively govern their mutual rights, obligations, and interactions over specific issues or regions.
-
B.
multilateral negotiation process
A multilateral negotiation process is a structured series of interactions among three or more parties with differing interests, aimed at reaching mutually acceptable agreements through communication, bargaining, and compromise.
-
C.
multinational mission mechanism
A multinational mission mechanism is a structured framework of processes, agreements, and coordinating bodies that enables multiple countries or organizations to collaboratively plan, resource, and execute a shared mission across borders.
-
D.
supranational entity
A supranational entity is an organization or institution formed by multiple sovereign states that delegates certain decision-making powers above the national level to pursue common policies or goals.
-
E.
supranational parliamentary assembly
A supranational parliamentary assembly is a representative legislative body composed of delegates from multiple sovereign states, empowered to deliberate, make decisions, and sometimes enact binding rules at a level above the nation-state.
- 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_69ca831ee390819095fae73400bbfafc |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:13 p.m.