Triple
T31775246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Territorial Gendarmerie units |
E811046
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional law enforcement formation |
C3496
|
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: regional law enforcement formation Context triple: [Territorial Gendarmerie units, instanceOf, regional law enforcement formation]
-
A.
law enforcement unit
chosen
A law enforcement unit is an organized group within a policing or security agency tasked with enforcing laws, maintaining public order, and conducting specialized operations or investigations.
-
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.
regional joint task force
A regional joint task force is a collaborative, multi-agency or multi-national organization formed within a specific geographic area to coordinate and execute integrated operations toward shared security, emergency response, or policy objectives.
-
D.
regional intelligence formation
Regional intelligence formation is the process by which localized knowledge, data, and contextual insights are gathered, synthesized, and structured within a specific geographic or cultural area to support informed decision-making and strategic action.
-
E.
defunct law enforcement agency
A defunct law enforcement agency is a former governmental body that once held official authority to enforce laws and maintain public order but has since been disbanded, merged, or otherwise ceased operations.
- 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_69f348e544a48190ab6e700b05f6438c |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:34 p.m.