Triple
T16570268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDICIA |
E402565
|
entity |
| Predicate | introducedAsResponseTo |
P767
|
FINISHED |
| Object | failures of savings and loan associations |
—
|
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: failures of savings and loan associations | Statement: [FDICIA, introducedAsResponseTo, failures of savings and loan associations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsResponseTo Context triple: [FDICIA, introducedAsResponseTo, failures of savings and loan associations]
-
A.
establishedInResponseTo
Indicates that something was created, initiated, or set up as a direct reaction to a specific event, condition, or stimulus.
-
B.
enactedInResponseTo
Indicates that one action, policy, or measure was carried out as a direct reaction to a specific prior event, condition, or stimulus.
-
C.
wasResponseTo
chosen
Indicates that one event, action, or communication occurred as a direct reply or reaction to a preceding event, action, or communication.
-
D.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
E.
originallyProposedAs
Indicates that one entity was first suggested, introduced, or put forward in the form or role of another entity.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e359580f548190a21afd148bc22d8d |
completed | April 18, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:16 a.m.