Triple
T16425223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NSC 10/5 directive |
E398925
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. government policy paper |
C1314
|
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: U.S. government policy paper Context triple: [NSC 10/5 directive, instanceOf, U.S. government policy paper]
-
A.
U.S. Department of Defense strategic document
A U.S. Department of Defense strategic document is an official, high-level publication that outlines long-term defense objectives, priorities, and plans for employing military resources to protect national security interests.
-
B.
United States federal document
chosen
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.
-
C.
USAID policy document
A USAID policy document is an official directive that establishes agency-wide principles, rules, and requirements guiding the planning, implementation, and oversight of U.S. foreign assistance programs.
-
D.
government strategy document
A government strategy document is an official, forward-looking plan that outlines a public authority’s long-term goals, priorities, and coordinated actions for addressing specific policy areas or national challenges.
-
E.
government report
A government report is an official document produced by a public agency that presents findings, data, analyses, or recommendations on matters of public policy, administration, or societal concern.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:09 a.m.