Triple
T85170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glass–Steagall Act |
E1713
|
entity |
| Predicate | responseTo |
P1128
|
FINISHED |
| Object | bank failures of the early 1930s |
—
|
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: bank failures of the early 1930s | Statement: [Glass–Steagall Act, responseTo, bank failures of the early 1930s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseTo Context triple: [Glass–Steagall Act, responseTo, bank failures of the early 1930s]
-
A.
wasResponseTo
Indicates that one event, action, or communication occurred as a direct reply or reaction to a preceding event, action, or communication.
-
B.
receivedSupportFrom
Indicates that one entity obtained help, resources, or backing from another entity.
-
C.
enactedInResponseTo
chosen
Indicates that one action, policy, or measure was carried out as a direct reaction to a specific prior event, condition, or stimulus.
-
D.
support
Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
-
E.
responsibleFor
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a250e401288190ba12322c9c5f07c9 |
completed | Feb. 28, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69a24eb59e808190811c20518f39b1cc |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.