Triple
T21189517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Security Information |
E522175
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | classified information category |
C18147
|
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: classified information category Context triple: [National Security Information, instanceOf, classified information category]
-
A.
U.S. national security classification category
chosen
A U.S. national security classification category is a designated level (e.g., Confidential, Secret, Top Secret) assigned to information whose unauthorized disclosure could harm national defense, foreign relations, or other protected government interests.
-
B.
classified report
A classified report is a formal document containing sensitive or restricted information that is protected by specific security protocols and only accessible to authorized individuals.
-
C.
administrative category
An administrative category is a classification used by organizations or governments to group entities, activities, or data for the purposes of management, regulation, and record-keeping.
-
D.
national security information
National security information is any classified or sensitive data whose unauthorized disclosure could reasonably be expected to harm a nation’s defense, foreign relations, intelligence activities, or overall security interests.
-
E.
federal government contractor category
A federal government contractor category is a classification that groups contractors based on characteristics such as size, ownership status, industry, or eligibility for specific federal procurement programs and set-asides.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 3:07 p.m.