Triple
T9541093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airborne Stand-Off Radar |
E230158
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military surveillance program |
C10566
|
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: military surveillance program Context triple: [Airborne Stand-Off Radar, instanceOf, military surveillance program]
-
A.
electronic surveillance program
An electronic surveillance program is a system that monitors, collects, and analyzes digital communications or electronic data to detect, track, or investigate activities of interest, often for security, intelligence, or law enforcement purposes.
-
B.
mass surveillance program
A mass surveillance program is a systematic, often government-led initiative that continuously collects, monitors, and analyzes large-scale data about populations to track behavior, communications, and activities.
-
C.
military program
chosen
A military program is an organized set of defense-related activities, projects, or initiatives designed to develop, maintain, or enhance a nation's armed forces capabilities and readiness.
-
D.
signals intelligence program
A signals intelligence program is a coordinated set of activities, technologies, and procedures designed to collect, process, analyze, and exploit electronic signals and communications for intelligence and security purposes.
-
E.
military project
A military project is a coordinated, goal-driven initiative undertaken by armed forces or defense organizations to develop, test, or deploy capabilities, technologies, or operations that enhance national security and military effectiveness.
- 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_69ca847b1b3081908f72bc932c17cc41 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:01 p.m.