Triple
T6029640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3 Commando Brigade |
E134267
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Marines formation |
C19791
|
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 Marines formation Context triple: [3 Commando Brigade, instanceOf, Royal Marines formation]
-
A.
Royal Navy and Army contingent
A Royal Navy and Army contingent is a combined military unit composed of personnel from both the Royal Navy and the British Army, organized for joint operations, ceremonial duties, or specific missions.
-
B.
French Army formation
A French Army formation is an organized military unit or grouping within the French Army, structured and equipped to conduct specific operational, tactical, or administrative functions.
-
C.
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.
-
D.
British Army position
A British Army position is a specific role or rank within the British Army’s organizational structure, defining an individual’s responsibilities, authority, and place in the military hierarchy.
-
E.
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.
- F. None of above. chosen
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_69c0087515148190a97475d412563865 |
completed | March 22, 2026, 3:19 p.m. |
Created at: March 22, 2026, 4:07 p.m.