Triple
T31842123
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centro Superior de Información de la Defensa |
E812837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | defence intelligence organization |
C13449
|
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: defence intelligence organization Context triple: [Centro Superior de Información de la Defensa, instanceOf, defence intelligence organization]
-
A.
defense intelligence organization
chosen
A defense intelligence organization is a specialized governmental or military entity responsible for collecting, analyzing, and disseminating information on foreign and domestic threats to support national security and defense decision-making.
-
B.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
C.
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.
-
D.
security and intelligence unit
A security and intelligence unit is an organized group responsible for gathering, analyzing, and acting on information to prevent threats and protect people, assets, and critical operations.
-
E.
public defense agency
A public defense agency is a government-funded organization that provides legal representation and related services to individuals who cannot afford private attorneys, typically in criminal proceedings.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:49 p.m.