Triple
T36629292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coldstream Guards Regimental Band |
E904265
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | British Army band |
C65463
|
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 band Context triple: [Coldstream Guards Regimental Band, instanceOf, British Army band]
-
A.
British brass band
A British brass band is a traditional ensemble consisting primarily of brass instruments and percussion, following a standardized instrumentation and often associated with community, colliery, and contesting music-making in the United Kingdom.
-
B.
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.
-
C.
Welsh brass band
A Welsh brass band is a community-based musical ensemble from Wales, typically comprising brass and percussion instruments, that performs traditional, ceremonial, and contemporary repertoire rooted in Welsh cultural and mining-town heritage.
-
D.
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.
-
E.
British Army order
A British Army order is an official directive issued by a competent military authority within the British Army that prescribes specific actions, procedures, or policies to be followed by subordinate personnel.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:11 p.m.