Triple
T9946686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Criminal Justice Information Services Security Policy |
E195221
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FBI policy document |
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: FBI policy document Context triple: [Criminal Justice Information Services Security Policy, instanceOf, FBI policy document]
-
A.
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.
-
B.
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.
-
C.
security agency
A security agency is an organization that provides professional protection, surveillance, and risk management services to safeguard people, property, and information.
-
D.
U.S. intelligence product
A U.S. intelligence product is an analyzed and synthesized information output, derived from collected data and sources, that informs government decision-makers about foreign or domestic threats, opportunities, and strategic developments.
-
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_69ca82e96a108190932bd1fc4acd73a0 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:45 p.m.