Triple
T12402937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | APEC member governments |
E296305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intergovernmental body member |
C19334
|
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: intergovernmental body member Context triple: [APEC member governments, instanceOf, intergovernmental body member]
-
A.
intergovernmental organization participant
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.
-
B.
intergovernmental organization membership
chosen
Intergovernmental organization membership is the formal status by which a state or other eligible entity participates as a member in an intergovernmental organization, with associated rights, obligations, and privileges.
-
C.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
D.
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.
-
E.
international organization membership category
A classification that specifies the type or status of a member (such as full, associate, observer, or partner) within an international organization.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:55 p.m.