Triple
T11017506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telemark Battalion |
E260400
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mechanized infantry battalion |
C29021
|
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: mechanized infantry battalion Context triple: [Telemark Battalion, instanceOf, mechanized infantry battalion]
-
A.
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.
-
B.
armored infantry division
An armored infantry division is a large, combined-arms military formation that integrates mechanized infantry, tanks, artillery, and support units to conduct sustained offensive and defensive ground operations.
-
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.
infantry platoon
An infantry platoon is a small, tactical military unit of foot soldiers, typically composed of several squads and led by a platoon leader, organized to conduct coordinated ground combat operations.
-
E.
airborne infantry battalion
An airborne infantry battalion is a highly mobile, lightly equipped military unit trained and organized to deploy rapidly by air and conduct combat operations, often via parachute or air assault, to seize and hold key terrain behind or ahead of front lines.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:25 p.m.