Triple
T4344717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Financial Stability Facility |
E97871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | temporary crisis resolution mechanism |
C15106
|
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: temporary crisis resolution mechanism Context triple: [European Financial Stability Facility, instanceOf, temporary crisis resolution mechanism]
-
A.
crisis
A crisis is a critical turning point or period of intense difficulty and instability that demands urgent decision-making and action to prevent severe negative consequences.
-
B.
crisis management activity
A crisis management activity is a coordinated task or operation undertaken to prepare for, respond to, mitigate, or recover from an unexpected disruptive event that threatens an organization’s objectives or stakeholders.
-
C.
crisis-management mandate
A crisis-management mandate is a formal directive that defines the authority, responsibilities, and procedures an organization must follow to prepare for, respond to, and recover from critical incidents or emergencies.
-
D.
institutional crisis
An institutional crisis is a severe breakdown or loss of legitimacy in the structures, rules, or authority of key organizations or systems, undermining their ability to function effectively and maintain public trust.
-
E.
crisis response organization
chosen
A crisis response organization is an entity that rapidly coordinates resources, personnel, and communication to assess, manage, and mitigate emergencies or disasters affecting people, infrastructure, or the environment.
- 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_69b34548402c819085ab68b27c235a87 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:15 p.m.