Triple
T22761254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Task Force Helmand |
E562995
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British-led military unit |
C41891
|
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: British-led military unit Context triple: [Task Force Helmand, instanceOf, British-led military unit]
-
A.
British-organized force
chosen
A British-organized force is a military or paramilitary unit that is raised, structured, trained, equipped, or commanded under the authority or direction of the British government or its agents.
-
B.
British volunteer defence force
A British volunteer defence force is a non-regular, citizen-based military organization formed to supplement the professional armed forces in times of war, crisis, or national emergency.
-
C.
British Commonwealth military formation
A British Commonwealth military formation is an organized, hierarchical combat or support unit composed of personnel and resources contributed by two or more member states of the British Commonwealth, operating under a unified command structure for joint military objectives.
-
D.
British paramilitary police force
A British paramilitary police force is a law enforcement body organized, trained, and equipped along military lines to perform policing, public order, and security duties while operating under civilian authority.
-
E.
British colonial regiment
A British colonial regiment is a military unit raised, organized, and commanded by the British Empire from its overseas colonies, typically composed of local recruits led by British officers to serve imperial defense and expansion.
- 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_69e24552e11c81909c2d61578a558bd7 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 17, 2026, 3:26 p.m.