Triple
T6636403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | División de Inteligencia |
E150463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | unidad de inteligencia militar |
C549
|
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: unidad de inteligencia militar Context triple: [División de Inteligencia, instanceOf, unidad de inteligencia militar]
-
A.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
B.
defense intelligence organization
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.
-
C.
intelligence organization unit
chosen
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.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
E.
special operations forces unit
A special operations forces unit is a highly trained, small military team designed to conduct specialized, high-risk missions such as reconnaissance, direct action, counterterrorism, and unconventional warfare, often in politically sensitive or denied environments.
- 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_69c687f0ceb08190bf40807bfc605fa5 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:59 p.m.