Triple
T24471240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Battalion, 5th Cavalry Regiment |
E617105
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combined arms battalion |
C49042
|
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: combined arms battalion Context triple: [1st Battalion, 5th Cavalry Regiment, instanceOf, combined arms battalion]
-
A.
combat support battalion
A combat support battalion is a military unit that provides specialized capabilities—such as engineering, intelligence, communications, and logistics—to enhance and sustain the combat effectiveness of frontline forces.
-
B.
U.S. Army battalion
A U.S. Army battalion is a mid-sized tactical unit, typically consisting of 300–1,000 soldiers organized into several companies, capable of independent operations under a battalion commander.
-
C.
anti-tank battalion
An anti-tank battalion is a military unit organized, equipped, and trained specifically to detect, engage, and destroy enemy armored vehicles and tanks using specialized anti-armor weapons and tactics.
-
D.
armored brigade combat team
An armored brigade combat team is a highly mobile, heavily armored combined-arms military formation designed to conduct offensive and defensive ground operations using tanks, mechanized infantry, artillery, and support units.
-
E.
mechanized infantry battalion
A mechanized infantry battalion is a military unit composed of infantry soldiers equipped with armored vehicles that provide protected mobility, firepower, and support for rapid, combined-arms operations on 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:20 a.m.