Triple
T3338013
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Committee on Hemispheric Security |
E70186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | OAS body |
C3196
|
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: OAS body Context triple: [Committee on Hemispheric Security, instanceOf, OAS body]
-
A.
OAS legal instrument
An OAS legal instrument is a formal, binding or non-binding document adopted within the framework of the Organization of American States that establishes rights, obligations, standards, or procedures for its member states in areas such as democracy, human rights, security, and development.
-
B.
public communication body
A public communication body is an organization or institution responsible for disseminating information, messages, or media content to the general public through various communication channels.
-
C.
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.
-
D.
programmatic body
A programmatic body is a systematically organized collection of rules, procedures, or code that governs and coordinates the behavior and interactions within a defined system or domain.
-
E.
organ of the Organization of American States
chosen
An organ of the Organization of American States is an official institutional body established by the OAS Charter to perform specific functions—such as political, judicial, administrative, or advisory roles—in support of the organization’s purposes and decision-making processes.
- 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_69ad85a24f208190bcf83131bfed3521 |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:12 p.m.