Triple
T31013041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gendarmerie Criminal Department |
E790256
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | forensic law enforcement agency |
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: forensic law enforcement agency Context triple: [Gendarmerie Criminal Department, instanceOf, forensic law enforcement agency]
-
A.
law enforcement agency network
A law enforcement agency network is an interconnected system of local, regional, and national policing and investigative bodies that share information, resources, and coordination mechanisms to prevent, detect, and respond to crime and public safety threats.
-
B.
law enforcement agency category
A law enforcement agency category is a classification that groups agencies based on their jurisdiction, function, organizational structure, or level of authority within the legal and public safety system.
-
C.
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.
-
D.
law enforcement office
A law enforcement office is a physical workplace where police or other authorized agencies coordinate, manage, and support activities related to maintaining public safety and enforcing laws.
-
E.
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.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 8:57 p.m.