Triple
T25378071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern African Development Community Standby Force |
E633106
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional standby force |
C50086
|
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: regional standby force Context triple: [Southern African Development Community Standby Force, instanceOf, regional standby force]
-
A.
regional joint task force
A regional joint task force is a collaborative, multi-agency or multi-national organization formed within a specific geographic area to coordinate and execute integrated operations toward shared security, emergency response, or policy objectives.
-
B.
regional land command
A regional land command is a military organizational structure responsible for planning, directing, and coordinating all land-based operations and forces within a defined geographic area.
-
C.
occupation force
An occupation force is a military presence deployed by a controlling power to maintain authority, security, and administration over a captured or foreign territory.
-
D.
Japan Ground Self-Defense Force unit
A Japan Ground Self-Defense Force unit is an organized, mission-specific formation of personnel and equipment within Japan’s land-based military, structured to conduct defense, security, and support operations under national and international mandates.
-
E.
U.S. National Reserve
A U.S. National Reserve is a federally protected area of land or water designated to conserve natural, cultural, or historical resources while allowing for managed public use and enjoyment.
- F. None of above. chosen
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_69e75a90c0dc819092f928b6ea0ecc72 |
completed | April 21, 2026, 11:08 a.m. |
Created at: April 21, 2026, 1:38 p.m.