Triple
T496418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Intelligence Program |
E10303
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intelligence funding framework |
C2944
|
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: intelligence funding framework Context triple: [Military Intelligence Program, instanceOf, intelligence funding framework]
-
A.
intelligence organization unit
An intelligence organization unit is a structured group within an intelligence agency responsible for collecting, analyzing, and disseminating information to support decision-making and security objectives.
-
B.
intelligence officer
An intelligence officer is a professional responsible for collecting, analyzing, and disseminating sensitive information to support national security, military operations, or organizational decision-making.
-
C.
intelligence agency division
A specialized organizational unit within an intelligence agency responsible for focused functions such as collection, analysis, operations, or support in pursuit of national security objectives.
-
D.
intelligence oversight committee
An intelligence oversight committee is a formal body responsible for monitoring, reviewing, and regulating the activities of intelligence agencies to ensure legality, accountability, and alignment with democratic norms and national interests.
-
E.
science agency
A science agency is an organization, typically governmental or intergovernmental, that funds, coordinates, and oversees scientific research and development to advance knowledge and inform policy.
- F. None of above. chosen
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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.