Triple
T29381134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komando Cadangan Strategis Angkatan Darat |
E745137
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | strategic reserve force |
C54473
|
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: strategic reserve force Context triple: [Komando Cadangan Strategis Angkatan Darat, instanceOf, strategic reserve force]
-
A.
standby force
A standby force is a pre-organized, trained, and readily available group of personnel and resources maintained in reserve for rapid deployment in response to emergencies, crises, or specific operational needs.
-
B.
armed forces reserve
chosen
An armed forces reserve is a military component composed of trained personnel who are not in full-time active service but can be mobilized to support or augment regular forces during emergencies, conflicts, or special operations.
-
C.
naval reserve force
A naval reserve force is a component of a nation's navy composed of trained personnel who serve part-time and can be mobilized to support or augment regular naval operations during emergencies, conflicts, or special missions.
-
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.
auxiliary military force
An auxiliary military force is a supplementary, often non-regular or part-time armed organization that supports a nation’s primary military through additional manpower, specialized skills, or local defense roles.
- 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_69f0a79cfd5481909b4dde750cb8d2c6 |
completed | April 28, 2026, 12:27 p.m. |
Created at: April 28, 2026, 2:35 p.m.