Triple
T25768185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CIA KUBARK interrogation manual |
E648940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | classified government document |
C4034
|
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 government document Context triple: [CIA KUBARK interrogation manual, instanceOf, classified government document]
-
A.
government document collection
A government document collection is an organized set of official records, reports, laws, and publications produced or issued by governmental bodies, maintained for reference, accountability, and public access.
-
B.
classified report
chosen
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.
United States federal document
A United States federal document is an official record, form, publication, or communication created, issued, or maintained by a federal agency or branch of the U.S. government in the course of its authorized duties.
-
D.
government-sponsored documentation project
A government-sponsored documentation project is an officially funded and managed initiative to systematically collect, record, and preserve information, data, or cultural materials for public, administrative, or historical purposes.
-
E.
strategic document
A strategic document is a formal written plan that outlines an organization’s long-term goals, priorities, and actions for achieving its mission and competitive advantage.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 5:12 a.m.