Triple
T8587769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TP-UTVA |
E203348
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Government’s Foreign and Security Policy Committee |
C24152
|
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: Government’s Foreign and Security Policy Committee Context triple: [TP-UTVA, instanceOf, Government’s Foreign and Security Policy Committee]
-
A.
foreign affairs committee
A foreign affairs committee is a legislative body responsible for overseeing and shaping a government's foreign policy, international agreements, and diplomatic relations.
-
B.
government committee
A government committee is a formally established group of officials or representatives tasked with studying specific issues, developing recommendations, and overseeing particular areas of public policy or administration.
-
C.
national security council-type body
chosen
A national security council-type body is a high-level governmental committee that coordinates and advises on national security, foreign policy, and defense strategy across relevant agencies and branches.
-
D.
parliamentary security organization
A parliamentary security organization is a specialized body responsible for protecting the legislature’s members, staff, visitors, facilities, and information while supporting the safe and orderly conduct of parliamentary business.
-
E.
UN budgetary committee
A UN budgetary committee is a formal body within the United Nations responsible for reviewing, negotiating, and recommending decisions on the organization’s budget, financial policies, and resource allocations among its programs and activities.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.