Triple
T27977110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US 72nd Heavy Tank Battalion |
E706519
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Army tank battalion |
C22556
|
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: United States Army tank battalion Context triple: [US 72nd Heavy Tank Battalion, instanceOf, United States Army tank battalion]
-
A.
U.S. Army battalion
chosen
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.
-
B.
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.
-
C.
U.S. Army armored division
A U.S. Army armored division is a large, combined-arms military formation centered on tanks and mechanized infantry, designed to conduct high-intensity, mobile ground combat operations.
-
D.
U.S. Army aviation battalion
A U.S. Army aviation battalion is a military unit that organizes, operates, and sustains multiple helicopter or fixed-wing aircraft companies to provide air assault, reconnaissance, transport, medical evacuation, and support capabilities to ground forces.
-
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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:41 p.m.