Triple
T7557390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 26th Yankee Brigade |
E178702
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Army National Guard unit |
C9194
|
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: Army National Guard unit Context triple: [26th Yankee Brigade, instanceOf, Army National Guard unit]
-
A.
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.
-
B.
U.S. Army regiment
A U.S. Army regiment is a traditional military unit designation that historically grouped multiple battalions or companies under a common lineage and identity, now used primarily for organizational, administrative, and ceremonial purposes rather than as a primary tactical formation.
-
C.
United States military formation
chosen
A United States military formation is an organized grouping of U.S. armed forces personnel and units, structured and deployed to conduct specific missions or operations under a defined command hierarchy.
-
D.
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.
-
E.
U.S. Army infantry brigade
A U.S. Army infantry brigade is a modular, combined-arms combat unit typically consisting of several infantry battalions and supporting elements, organized to conduct sustained ground operations across a range of 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_69c69f2da22c8190a50942ac20af70e8 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:50 p.m.