Triple
T9992491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Operations Task Group |
E196920
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military task group |
C2497
|
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: military task group Context triple: [Special Operations Task Group, instanceOf, military task group]
-
A.
Japanese naval task force
A Japanese naval task force is an organized, mission-focused grouping of Japanese warships, aircraft, and support vessels operating together under a unified command to achieve specific maritime objectives.
-
B.
fighter group
A fighter group is a military aviation unit composed of multiple fighter squadrons, organized to conduct coordinated air combat and support operations under a unified command.
-
C.
naval unit
A naval unit is an organized group of maritime military assets—such as ships, submarines, aircraft, and personnel—structured to conduct operations and missions at sea.
-
D.
military unit
chosen
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
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_69ca82f1678c819093d06320a05f16a4 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 8:50 p.m.