Triple
T34876484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Direction centrale de la sécurité publique |
E1005894
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | direction of the French National Police |
C3345
|
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: direction of the French National Police Context triple: [Direction centrale de la sécurité publique, instanceOf, direction of the French National Police]
-
A.
national gendarmerie force
A national gendarmerie force is a militarized police organization with nationwide jurisdiction, typically under both defense and interior ministries, responsible for law enforcement, public order, and security duties, especially in rural or strategic areas.
-
B.
police force
chosen
A police force is an organized body of officers empowered by a government to maintain public order, enforce laws, prevent and investigate crime, and protect citizens and property.
-
C.
department of France
A department of France is an administrative territorial division within the country, situated between the region and commune levels, responsible for local governance, public services, and implementation of national policies.
-
D.
local authority of France
A local authority of France is a decentralized public entity (such as a commune, department, or region) with its own elected council and administrative powers to manage local affairs within a defined territory under national law.
-
E.
polis
A polis is an ancient Greek city-state, functioning as an independent political, social, and religious community centered on an urban core and its surrounding territory.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4 p.m.