Triple
T1740639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Australian Signals Directorate |
E38224
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cyber security agency |
C3363
|
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: cyber security agency Context triple: [Australian Signals Directorate, instanceOf, cyber security agency]
-
A.
security agency
A security agency is an organization that provides professional protection, surveillance, and risk management services to safeguard people, property, and information.
-
B.
state security agency
chosen
A state security agency is a government organization responsible for protecting national security through intelligence gathering, counterintelligence, and enforcement activities aimed at preventing internal and external threats.
-
C.
component of the Cybersecurity and Infrastructure Security Agency
A component of the Cybersecurity and Infrastructure Security Agency is an organizational unit or program within CISA that carries out specific cybersecurity, infrastructure protection, emergency communications, or risk management functions in support of the agency’s mission.
-
D.
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.
-
E.
domestic intelligence agency
A domestic intelligence agency is a government organization responsible for collecting, analyzing, and acting on information related to internal security threats within a country's borders, such as terrorism, espionage, and subversion.
- 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_69a8862b01a48190ab47209063af82d9 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:30 p.m.