Triple
T15858811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Comsubin Divers Group |
E384528
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military special forces unit |
C20321
|
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 special forces unit Context triple: [Comsubin Divers Group, instanceOf, military special forces unit]
-
A.
special operations forces unit
chosen
A special operations forces unit is a highly trained, small military team designed to conduct specialized, high-risk missions such as reconnaissance, direct action, counterterrorism, and unconventional warfare, often in politically sensitive or denied environments.
-
B.
military unit
A military unit is an organized group of armed personnel structured under a defined command hierarchy to perform specific tactical or operational missions.
-
C.
military special operations command
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
D.
special operations support unit
A special operations support unit is a specialized organization that provides logistical, intelligence, technical, and operational assistance to special operations forces to enable and sustain their missions.
-
E.
Marine Corps special operations unit
A Marine Corps special operations unit is an elite, highly trained military formation specializing in direct action, special reconnaissance, and unconventional warfare in maritime and littoral 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_69d86da422088190aac39e32e6c68429 |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:50 a.m.