Triple
T18309863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hakkoda Mountains incident |
E438591
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military training disaster |
C8259
|
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: military training disaster Context triple: [Hakkoda Mountains incident, instanceOf, military training disaster]
-
A.
disaster
A disaster is a sudden, disruptive event—natural or human-made—that causes significant harm to people, property, or the environment and overwhelms normal coping capacities.
-
B.
emergency management training organization
An emergency management training organization designs and delivers specialized education, simulations, and certification programs to prepare individuals and agencies to effectively prevent, respond to, and recover from emergencies and disasters.
-
C.
military training doctrine
A military training doctrine is a formalized set of principles, methods, and standards that guides how armed forces prepare personnel and units to plan, fight, and support operations effectively and consistently.
-
D.
military event
chosen
A military event is an occurrence involving organized armed forces engaging in actions such as combat, maneuvers, operations, or strategic activities within a specific time and place.
-
E.
sports-related disaster
A sports-related disaster is a catastrophic event occurring in connection with a sporting activity or venue—such as during games, training, or associated travel—that results in significant injury, loss of life, or large-scale harm to people or property.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:36 a.m.