Triple
T20761526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ratbat |
E510986
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Surveillance specialist |
C24952
|
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: Surveillance specialist Context triple: [Ratbat, instanceOf, Surveillance specialist]
-
A.
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.
-
B.
computer security specialist
A computer security specialist is a professional who protects computer systems, networks, and data from unauthorized access, attacks, and vulnerabilities by implementing, monitoring, and improving security measures.
-
C.
CIA security contractor
A CIA security contractor is a private-sector professional or firm hired by the Central Intelligence Agency to provide specialized security, protection, and risk management services in support of intelligence operations and facilities.
-
D.
intelligence, surveillance, and reconnaissance enterprise
chosen
An intelligence, surveillance, and reconnaissance enterprise is an integrated system of people, processes, and technologies that collects, analyzes, and disseminates information to provide timely situational awareness and decision support.
-
E.
military deception specialist
A military deception specialist is an expert who plans, coordinates, and executes operations designed to mislead adversaries about friendly capabilities, intentions, and actions to gain strategic or tactical advantage.
- 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_69e0b4c909ec8190b05987f1639513f6 |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:35 p.m.