Triple
T37857981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barnard Bee’s brigade near Henry House Hill |
E944244
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | infantry brigade deployment |
C56563
|
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: infantry brigade deployment Context triple: [Barnard Bee’s brigade near Henry House Hill, instanceOf, infantry brigade deployment]
-
A.
army formation
An army formation is an organized arrangement of military units and personnel on the battlefield or during maneuvers, designed to optimize command, movement, and combat effectiveness.
-
B.
brigade-level formation
chosen
A brigade-level formation is a mid-sized military unit, typically composed of several battalions and supporting elements, capable of independent operations under a unified command.
-
C.
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.
-
D.
Continental Army brigade formation
A Continental Army brigade formation was a tactical military unit composed of several regiments organized under a brigadier general, arranged on the battlefield to coordinate infantry, artillery, and support elements during the American Revolutionary War.
-
E.
airborne infantry brigade
An airborne infantry brigade is a highly mobile, light infantry formation trained and equipped to deploy rapidly by air, including parachute or air assault operations, to seize and hold key objectives behind or ahead of enemy lines.
- 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_69f76eee2f9c8190b1272aa2ee55ebf5 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:19 p.m.