Triple
T21154650
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intelligence Weapons Instructor Course |
E521280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | intelligence training course |
C15107
|
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 training course Context triple: [Intelligence Weapons Instructor Course, instanceOf, intelligence training course]
-
A.
intelligence analysis course
chosen
An intelligence analysis course teaches students systematic methods, tools, and critical thinking skills to collect, evaluate, and interpret information for informed decision-making in security, policy, or organizational contexts.
-
B.
intelligence program
An intelligence program is a software system designed to collect, process, analyze, and interpret data to generate actionable insights or decisions that mimic or support human cognitive capabilities.
-
C.
intelligence assessment
An intelligence assessment is a systematic evaluation process used to measure, analyze, and interpret an individual’s or group’s cognitive abilities, problem-solving skills, and related mental capacities for decision-making or diagnostic purposes.
-
D.
intelligence front
An intelligence front is an ostensibly legitimate organization or entity that covertly serves as a cover for intelligence-gathering, espionage, or other clandestine activities.
-
E.
intelligence directive
An intelligence directive is a formal instruction or guiding framework that defines the objectives, priorities, and constraints for the collection, analysis, and dissemination of intelligence information.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:58 p.m.