Triple
T8533743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2nd Assault Amphibian Battalion |
E202020
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | assault amphibian unit |
C4162
|
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: assault amphibian unit Context triple: [2nd Assault Amphibian Battalion, instanceOf, assault amphibian unit]
-
A.
amphibious assault ship class
An amphibious assault ship class is a group of large naval vessels designed to deploy, support, and command marine forces in amphibious operations using a combination of helicopters, landing craft, and sometimes short takeoff and vertical landing aircraft.
-
B.
naval infantry
chosen
Naval infantry are specialized military forces trained and equipped to conduct amphibious assaults and other combat operations from the sea onto hostile or potentially hostile shores.
-
C.
rescue unit
A rescue unit is an organized team equipped and trained to respond rapidly to emergencies, providing aid, protection, and extraction of people or animals from dangerous or life-threatening situations.
-
D.
paratrooper unit
A paratrooper unit is a specialized military formation trained and equipped to deploy from aircraft by parachute to conduct airborne assaults, rapid insertions, and operations behind enemy lines.
-
E.
Marine Air-Ground Task Force logistics element
The Marine Air-Ground Task Force logistics element is the component responsible for providing comprehensive combat service support—including supply, maintenance, transportation, health services, and engineering—to sustain the MAGTF’s operations across all domains.
- 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_69ca832355b08190b8b6a4ab4a4a3554 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:17 p.m.