Triple
T11664187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Army positions in First Battle of Bull Run |
E277201
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | order of battle element |
C2497
|
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: order of battle element Context triple: [Union Army positions in First Battle of Bull Run, instanceOf, order of battle element]
-
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.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
C.
U.S. Army organizational element
A U.S. Army organizational element is a structured unit of soldiers, equipment, and command relationships designed to perform specific missions within the Army’s overall force hierarchy.
-
D.
component of land forces
A component of land forces is an organized, functionally distinct element of an army’s ground combat structure, such as infantry, armor, artillery, or support units, that contributes specific capabilities to land operations.
-
E.
British Army organizational element
A British Army organizational element is a defined structural unit—such as a section, platoon, company, battalion, brigade, or division—comprising personnel, equipment, and command relationships arranged to perform specific military roles within the Army’s hierarchy.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.