Triple
T10439935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Guard Fife and Drum Corps |
E246141
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army military band |
C4936
|
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: United States Army military band Context triple: [Old Guard Fife and Drum Corps, instanceOf, United States Army military band]
-
A.
military band system
chosen
A military band system is an organized framework of personnel, instruments, procedures, and protocols that enables armed forces musical units to perform ceremonial, representational, and morale-building functions.
-
B.
HBCU marching band
An HBCU marching band is a high-energy collegiate ensemble from a Historically Black College or University that blends precision marching, show-style drill, and dynamic musical performances rooted in Black cultural traditions.
-
C.
United States Army signal brigade
A United States Army signal brigade is a specialized military unit responsible for planning, installing, operating, and maintaining tactical and strategic communications and information systems to support command and control across the battlefield.
-
D.
drum and bugle corps
A drum and bugle corps is a marching musical ensemble, typically featuring brass instruments, percussion, and a color guard, that performs choreographed field shows and parades.
-
E.
U.S. Army battalion
A U.S. Army battalion is a mid-sized tactical unit, typically consisting of 300–1,000 soldiers organized into several companies, capable of independent operations under a battalion commander.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:15 p.m.