Triple
T32729097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Swedish Amphibious Corps |
E836900
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | marine infantry force |
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 force Context triple: [Swedish Amphibious Corps, instanceOf, marine infantry force]
-
A.
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.
-
B.
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.
-
C.
mine countermeasures force
A mine countermeasures force is a specialized naval unit equipped, trained, and organized to detect, classify, neutralize, and dispose of naval mines to ensure safe maritime operations.
-
D.
United States Marine Corps assault amphibian battalion
A United States Marine Corps assault amphibian battalion is a specialized mechanized unit that employs amphibious assault vehicles to transport Marines, equipment, and supplies from ship to shore and conduct sustained operations ashore in support of expeditionary and amphibious missions.
-
E.
reconnaissance Marine
A reconnaissance Marine is a highly trained member of the Marine Corps specializing in stealthy intelligence gathering, surveillance, and special operations in hostile or uncertain environments.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:11 a.m.