Triple
T29892543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quick Reaction Teams |
E759191
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rapid response force |
C15939
|
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: rapid response force Context triple: [Quick Reaction Teams, instanceOf, rapid response force]
-
A.
rapid deployment military force
A rapid deployment military force is a highly mobile, well-trained unit designed to be quickly transported and deployed worldwide to respond to emerging crises, conflicts, or humanitarian emergencies.
-
B.
rapid reaction force
chosen
A rapid reaction force is a highly mobile, quickly deployable military or security unit designed to respond immediately to emerging threats, crises, or contingencies.
-
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.
federal emergency response team
A federal emergency response team is a coordinated group of government professionals and resources mobilized to prepare for, respond to, and support recovery from large-scale disasters and public emergencies across jurisdictions.
-
E.
special operations forces unit
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.
- 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_69f2245f1cf88190978c70d1a1d2cb73 |
completed | April 29, 2026, 3:31 p.m. |
Created at: April 29, 2026, 6:03 p.m.