Triple
T35953163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolution Trust Corporation |
E1039783
|
entity |
| Predicate | typeOfCrisisAddressed |
P93977
|
FINISHED |
| Object | banking 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: banking crisis | Statement: [Resolution Trust Corporation, typeOfCrisisAddressed, banking crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfCrisisAddressed Context triple: [Resolution Trust Corporation, typeOfCrisisAddressed, banking crisis]
-
A.
crisisAddressed
Indicates that an entity has taken action to respond to, manage, or resolve a specific crisis.
-
B.
typeOfCrisis
chosen
Indicates the specific category or nature of a crisis that an entity is experiencing or associated with.
-
C.
typeOfCrisisManagement
Indicates the specific approach or method used to manage, respond to, or resolve a crisis situation.
-
D.
crisisManagement
Indicates the relationship in which an entity plans for, responds to, and mitigates the impact of disruptive or emergency situations.
-
E.
crisisRelatedTo
Indicates a relationship where one situation, event, or condition is connected to, associated with, or relevant to a crisis.
- 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_69f76e25ea488190b7cee970b3e70382 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a020243e2b4819086dbfdcf4372405e |
completed | May 11, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_6a0200f585bc8190b774c54cec409b00 |
completed | May 11, 2026, 4:16 p.m. |
Created at: May 3, 2026, 4:07 p.m.