Triple
T32595197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | joint special operations task group |
E833183
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special operations task group |
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: special operations task group Context triple: [joint special operations task group, instanceOf, special operations task group]
-
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.
special tactics squadron
A special tactics squadron is an elite military unit trained to conduct specialized, high-risk operations such as reconnaissance, direct action, and support of air and ground forces in complex or hostile environments.
-
C.
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.
-
D.
Special Purpose Marine Air-Ground Task Force
A Special Purpose Marine Air-Ground Task Force is a scalable, rapidly deployable, task-organized Marine Corps force combining ground, aviation, and logistics elements tailored to accomplish specific missions.
-
E.
special duties squadron
A special duties squadron is a military aviation unit tasked with highly specialized, often covert or unconventional missions that support broader operational 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 1:05 a.m.