Triple
T34253437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 369th Regimental Band |
E878807
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army band |
C47483
|
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 band Context triple: [369th Regimental Band, instanceOf, United States Army band]
-
A.
United States Army musical organization
chosen
A United States Army musical organization is a formal military unit composed of soldier-musicians that provides musical support for ceremonial, operational, and public relations missions of the U.S. Army.
-
B.
U.S. Army signal company
A U.S. Army signal company is a military unit responsible for establishing, operating, and maintaining communications and information systems that enable command and control across the battlefield.
-
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.
African American infantry regiment
An African American infantry regiment is a military unit composed primarily of Black soldiers organized for ground combat operations, historically formed under racially segregated structures within the armed forces.
-
E.
military band system
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.
- 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_69f349b3618481909df955b063f305b2 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:56 a.m.