Triple
T30189142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | States Parties to the 2005 Convention |
E767425
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governing body participant |
C22259
|
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: governing body participant Context triple: [States Parties to the 2005 Convention, instanceOf, governing body participant]
-
A.
governing body
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.
-
B.
governing body members
Individuals who hold official positions within a governing body and are responsible for making, interpreting, or enforcing policies and decisions on behalf of an organization, community, or state.
-
C.
intergovernmental organization participant
chosen
An intergovernmental organization participant is an entity, typically a sovereign state or recognized international body, that formally takes part in the activities, decision-making processes, and governance structures of an intergovernmental organization.
-
D.
partnership body
A partnership body is an organized group formed by two or more independent entities that collaborate under agreed arrangements to pursue shared goals, responsibilities, and benefits.
-
E.
governance entity
A governance entity is an individual, group, or organization with the authority and responsibility to establish, oversee, and enforce rules, policies, and decisions within a defined domain.
- 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_69f2247cc3d88190811dec3face94bf5 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:28 p.m.