Triple
T26681993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yankee Brigade |
E672636
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Guard brigade |
C51894
|
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: National Guard brigade Context triple: [Yankee Brigade, instanceOf, National Guard brigade]
-
A.
U.S. Army National Guard division
A U.S. Army National Guard division is a large, state-based military formation that can be federally mobilized, combining multiple brigades and support units to conduct sustained combat and support operations alongside active-duty Army forces.
-
B.
Air National Guard operations group
An Air National Guard operations group is a unit-level organization responsible for planning, directing, and executing the flying and operational support missions of an Air National Guard wing.
-
C.
Oklahoma Army National Guard unit
An Oklahoma Army National Guard unit is a state-based military organization composed of citizen-soldiers who train part-time to provide combat, support, and emergency response capabilities for both state and federal missions.
-
D.
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.
-
E.
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.
- 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_69eecda13424819092b17942c4edf722 |
completed | April 27, 2026, 2:44 a.m. |
Created at: April 27, 2026, 3:20 a.m.