Triple
T21640686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolt Forces |
E534082
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Egyptian 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: Egyptian military special forces unit Context triple: [Thunderbolt Forces, instanceOf, Egyptian 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.
Israeli Air Force unit
An Israeli Air Force unit is an organized military formation within Israel's air arm, responsible for executing specific operational, support, or training missions using assigned aircraft, personnel, and resources.
-
C.
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.
-
D.
Jewish military unit
A Jewish military unit is an organized armed force composed primarily of Jewish personnel, formed to conduct defense, combat, or security operations under a specific command structure.
-
E.
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.
- 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_69e0c465ae7481908577b7209fdb2a77 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:35 p.m.