Triple
T13001364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Security Program |
E322176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | security studies program |
C30428
|
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: security studies program Context triple: [International Security Program, instanceOf, security studies program]
-
A.
security research advocacy program
A security research advocacy program is an organized initiative that promotes, supports, and coordinates ethical security research and responsible vulnerability disclosure between researchers, organizations, and the broader community.
-
B.
national security law program
A national security law program is an academic or training course of study that focuses on the legal frameworks, institutions, and policies governing a nation’s defense, intelligence, and security operations.
-
C.
international affairs program
chosen
An international affairs program is an academic course of study that examines global politics, economics, law, and culture to prepare students for careers in diplomacy, policy analysis, and international organizations.
-
D.
military program
A military program is an organized set of defense-related activities, projects, or initiatives designed to develop, maintain, or enhance a nation's armed forces capabilities and readiness.
-
E.
Diplomatic Security Service program
A Diplomatic Security Service program is an organized set of policies, resources, and operations designed to protect diplomatic personnel, facilities, and information while supporting secure international engagement.
- 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_69d807657e8c8190bd9435ee2f823845 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:47 p.m.