Triple
T17203925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Special Service Brigade |
E417550
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Army commando formation |
C1740
|
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 Army commando formation Context triple: [1st Special Service Brigade, instanceOf, British Army commando formation]
-
A.
Royal Marines formation
A Royal Marines formation is an organized, mission-tailored military unit of the Royal Marines, structured and equipped to conduct amphibious, littoral, and expeditionary operations under a unified command.
-
B.
British Army organizational element
chosen
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.
-
C.
Canadian Army formation
A Canadian Army formation is an organized, hierarchical grouping of military units (such as brigades or divisions) structured to conduct land operations under a unified command within the Canadian Armed Forces.
-
D.
British Army deployment
British Army deployment is the organized assignment and movement of British Army personnel and resources to specific locations or operations to fulfill military objectives and commitments.
-
E.
British Army custom
A British Army custom is a traditional, informally codified practice or ritual observed by soldiers that reflects the Army’s history, values, and regimental identity.
- 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_69d886d6ba8c819093215917b3d01689 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:38 a.m.