Triple
T37167500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuerpo Técnico de Investigación |
E920828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | criminal investigation body |
C2354
|
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: criminal investigation body Context triple: [Cuerpo Técnico de Investigación, instanceOf, criminal investigation body]
-
A.
criminal investigation unit
chosen
A criminal investigation unit is a specialized law enforcement team responsible for systematically gathering, analyzing, and preserving evidence to identify suspects, solve crimes, and support successful prosecution.
-
B.
law enforcement body
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.
-
C.
investigative agency
An investigative agency is an organized entity that conducts systematic inquiries and gathers evidence to uncover facts, resolve disputes, or support legal and security-related decisions.
-
D.
public security organ
A public security organ is a government agency responsible for maintaining public order, preventing and investigating crimes, and safeguarding the security and stability of society.
-
E.
criminal justice policy advisory body
A criminal justice policy advisory body is a group of experts and stakeholders that analyzes data, evaluates existing practices, and provides recommendations to guide the development, reform, and implementation of criminal justice laws and policies.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.