Triple
T28418925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Löfven Cabinet I |
E719886
|
entity |
| Predicate | budgetCrisis |
P150516
|
FINISHED |
| Object | 2014 Swedish government crisis |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 2014 Swedish government crisis | Statement: [Löfven Cabinet I, budgetCrisis, 2014 Swedish government crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: budgetCrisis Context triple: [Löfven Cabinet I, budgetCrisis, 2014 Swedish government crisis]
-
A.
budgetDefeat
chosen
Indicates that a proposed budget has been rejected or failed to pass in a decision-making process.
-
B.
budget
Indicates that an entity allocates, plans, or assigns specific financial resources for another entity, activity, or time period.
-
C.
budgetaryEffect
Indicates the financial impact or change in budget resulting from a particular action, decision, or policy.
-
D.
majorCrisis
Indicates a severe, high-impact crisis or emergency situation affecting an entity or system.
-
E.
budgetFunction
Indicates a relationship where a specific budgeting rule or formula determines how resources or funds are allocated or constrained for an entity or activity.
- F. None of above.
Provenance (3 batches)
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_69eff6f1c5088190bc24bfbf92f9c017 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:32 a.m.