Triple
T82921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Security Council of the United States |
E1666
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | national security council |
C308
|
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: national security council Context triple: [National Security Council of the United States, instanceOf, national security council]
-
A.
national government
A national government is the central authority of a sovereign state responsible for creating and enforcing laws, managing public policy, and representing the nation domestically and internationally.
-
B.
central government
The central government is the primary national authority that exercises overarching political, legislative, and administrative control over a state, coordinating and regulating functions that affect the country as a whole.
-
C.
federal government
The federal government is the central governing authority of a nation that holds supreme power over national affairs, such as defense, foreign policy, and regulation of interstate matters, while sharing sovereignty with regional or state governments.
-
D.
governing council
chosen
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
E.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.