Triple
T455657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dirty Thirties |
E7226
|
entity |
| Predicate | prompted |
P693
|
FINISHED |
| Object | creation of the Soil Conservation Service |
—
|
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: creation of the Soil Conservation Service | Statement: [Dirty Thirties, prompted, creation of the Soil Conservation Service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prompted Context triple: [Dirty Thirties, prompted, creation of the Soil Conservation Service]
-
A.
triggered
chosen
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
B.
demanded
Indicates that one entity forcefully or insistently requested something from another entity.
-
C.
promotes
Indicates that one entity actively supports, advances, or encourages the growth, adoption, or success of another entity or outcome.
-
D.
motivated
Indicates that one entity provides a reason, drive, or incentive that causes another entity to act or behave in a certain way.
-
E.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by 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_69a2e7e5c5bc8190a1dc8178218fba40 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ef9f772c8190863399c5ee1378fe |
completed | Feb. 28, 2026, 1:37 p.m. |
| PD | Predicate disambiguation | batch_69a2ede4de008190b5a6c159e741522e |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.