Triple
T8019581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silverado Savings and Loan |
E186704
|
entity |
| Predicate | failureDate |
P37360
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [Silverado Savings and Loan, failureDate, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failureDate Context triple: [Silverado Savings and Loan, failureDate, 1988]
-
A.
decayDate
Indicates the date on which something ceases to be valid, effective, or usable (i.e., when it expires or decays).
-
B.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
C.
collapseDate
chosen
Indicates the date on which something structurally or functionally failed, broke down, or ceased to exist.
-
D.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
E.
finalDefeatDate
Indicates the date on which an entity was ultimately and conclusively defeated.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8bc90081909f6f5878e6f1f241 |
completed | March 31, 2026, 3:24 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:20 p.m.