Triple
T13601716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Mutual |
E324957
|
entity |
| Predicate | collapseContext |
P4060
|
FINISHED |
| Object | 2008 global financial 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: 2008 global financial crisis | Statement: [Washington Mutual, collapseContext, 2008 global financial crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collapseContext Context triple: [Washington Mutual, collapseContext, 2008 global financial crisis]
-
A.
collapseEvent
Indicates an event in which a structure, system, or entity suddenly falls apart, fails, or loses its integrity.
-
B.
collapsedDueTo
Indicates that one entity fell down, caved in, or structurally failed as a result of another specified cause or factor.
-
C.
closureContext
Indicates the surrounding scope or environment in which an operation, expression, or function is defined and executed, capturing the variables and bindings available to it.
-
D.
collapsedWith
Indicates that one entity fell down or caved in together with another entity, typically as part of the same collapse event.
-
E.
collapsedDuring
chosen
Indicates that one entity structurally failed or fell down while another specified event or process was occurring.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb07ad3f48190a2173e42c5cfedb1 |
completed | April 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_69dbae18eaf48190809e8b365856cde9 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.