Triple
T3078428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Mutual |
E64195
|
entity |
| Predicate | dateOfBankFailure |
P37360
|
FINISHED |
| Object | 2008-09-25 |
—
|
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-09-25 | Statement: [Washington Mutual, dateOfBankFailure, 2008-09-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfBankFailure Context triple: [Washington Mutual, dateOfBankFailure, 2008-09-25]
-
A.
dateOfBankruptcyFiling
Indicates the specific date on which a person or organization formally filed for bankruptcy.
-
B.
liquidationDate
Indicates the date on which an entity is formally wound up, dissolved, or its assets are converted to cash in a liquidation process.
-
C.
withdrawalDate
Indicates the date on which a withdrawal action occurs or is recorded.
-
D.
collapseDate
chosen
Indicates the date on which something structurally or functionally failed, broke down, or ceased to exist.
-
E.
immediateCauseDate
Indicates the specific date on which an event or condition directly caused another event or outcome to occur.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1a86a848190a47ca127cc7e6326 |
completed | March 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:02 p.m.