Triple
T743801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Parliament Security Service |
E15297
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | internal security body |
C3226
|
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: internal security body Context triple: [European Parliament Security Service, instanceOf, internal security body]
-
A.
interior ministry
The interior ministry is a government department responsible for domestic affairs, including internal security, public administration, civil registration, and often oversight of police and emergency services.
-
B.
state security agency
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.
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.
-
D.
law enforcement body
chosen
A law enforcement body is an organized governmental agency responsible for maintaining public order, preventing and investigating crime, and enforcing laws within a defined jurisdiction.
-
E.
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.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.