Triple
T15342776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Operation Unicorn |
E366838
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | contingency plan |
C11101
|
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: contingency plan Context triple: [Operation Unicorn, instanceOf, contingency plan]
-
A.
plan
chosen
A plan is a structured set of intended actions and decisions, organized over time and resources, to achieve specific goals or outcomes.
-
B.
long-term plan
A long-term plan is a structured, forward-looking strategy that outlines major goals and the sequence of actions needed to achieve them over an extended period of time.
-
C.
BCP
BCP is a Business Continuity Plan that outlines procedures and resources to ensure critical business functions continue or are quickly restored during and after a disruption.
-
D.
road transport contingency plan
A road transport contingency plan is a predefined set of strategies and procedures designed to maintain or quickly restore road-based logistics and mobility during disruptions, emergencies, or unexpected events.
-
E.
emergency preparedness program
An emergency preparedness program is a coordinated set of plans, training, resources, and procedures designed to help individuals, organizations, or communities effectively prevent, respond to, and recover from emergencies and disasters.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:17 a.m.