Triple
T13044308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General Police Duties companies |
E327277
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Military Police sub-unit |
C30365
|
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: Royal Military Police sub-unit Context triple: [General Police Duties companies, instanceOf, Royal Military Police sub-unit]
-
A.
Canadian Army cavalry regiment
A Canadian Army cavalry regiment is a military unit historically composed of mounted soldiers and now typically equipped with armored vehicles, responsible for reconnaissance, security, and mobile combat operations.
-
B.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
C.
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.
-
D.
military unit component
chosen
A military unit component is an individual sub-unit or element, such as a squad, platoon, or company, that combines with others to form a larger organized military force.
-
E.
British Army organizational element
A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:56 p.m.