Triple
T31815568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IV Brig Aerotrans |
E812123
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rapid deployment force component |
C50084
|
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 deployment force component Context triple: [IV Brig Aerotrans, instanceOf, rapid deployment force component]
-
A.
rapid deployment military force
chosen
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.
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.
-
C.
rapidly deployable capacity
Rapidly deployable capacity is a scalable set of resources, capabilities, or infrastructure that can be quickly mobilized and activated to meet sudden or fluctuating demand.
-
D.
regional standby force
A regional standby force is a pre-organized, rapidly deployable military or security contingent maintained by a group of neighboring states to respond collectively to crises, conflicts, or emergencies within their shared region.
-
E.
NATO rapid reaction corps headquarters
The NATO Rapid Reaction Corps Headquarters is a high-readiness, multinational command element responsible for planning, coordinating, and directing rapid deployment and operations of NATO land forces in crisis or conflict.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:44 p.m.