Triple
T17691269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1 Assault Group Royal Marines |
E441032
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Royal Marines unit |
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 unit Context triple: [1 Assault Group Royal Marines, instanceOf, Royal Marines unit]
-
A.
Royal Marines formation
chosen
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.
battalion of the Welsh Guards
A battalion of the Welsh Guards is a major operational unit of this British Army infantry regiment, composed of several companies of soldiers trained and organized for ceremonial duties and frontline combat operations.
-
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.
Marine Raiders battalion
A Marine Raiders battalion is a specialized U.S. Marine Corps special operations unit organized, trained, and equipped to conduct direct action, special reconnaissance, and other high-risk missions in support of strategic and operational objectives.
-
E.
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.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:03 a.m.