Triple
T9294564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turkish Gendarmerie |
E223607
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military 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: military law enforcement agency Context triple: [Turkish Gendarmerie, instanceOf, military law enforcement agency]
-
A.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
B.
military personnel management agency
A military personnel management agency is an organization responsible for overseeing the recruitment, assignment, development, welfare, and separation of service members to ensure effective utilization and readiness of military human resources.
-
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.
paramilitary organization
A paramilitary organization is a structured group that operates with military-style training, hierarchy, and tactics but is not formally part of a recognized state's official armed forces.
-
E.
law enforcement unit
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.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
Created at: March 30, 2026, 7:35 p.m.