Triple
T3908576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Marine Division |
E87265
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Marine infantry division |
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: Marine infantry division Context triple: [1st Marine Division, instanceOf, Marine infantry division]
-
A.
regiment of the United States Marine Corps
A regiment of the United States Marine Corps is a mid-level, combat-capable organizational unit typically composed of several battalions, providing command, control, and support for large-scale Marine operations.
-
B.
airborne infantry division
An airborne infantry division is a large military formation of specially trained soldiers equipped and organized to deploy rapidly by air, typically via parachute or air assault, to seize and hold key objectives behind enemy lines.
-
C.
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.
-
D.
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.
-
E.
marine corps
The Marine Corps is a branch of a nation's armed forces specialized in expeditionary and amphibious warfare, trained to rapidly deploy and operate on land, sea, and air in support of national defense objectives.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.