Triple
T99760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volcker shock |
E2014
|
entity |
| Predicate | praisedFor |
P22
|
FINISHED |
| Object | decisively ending the Great Inflation |
—
|
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: decisively ending the Great Inflation | Statement: [Volcker shock, praisedFor, decisively ending the Great Inflation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: praisedFor Context triple: [Volcker shock, praisedFor, decisively ending the Great Inflation]
-
A.
awardFor
Indicates that something is given or granted as recognition or a prize for a particular achievement, work, or contribution.
-
B.
awardReceived
Indicates that an entity has been granted or honored with a specific award or recognition.
-
C.
historicallyPrizedFor
Indicates that something has been especially valued or esteemed for a particular quality, use, or significance in the past.
-
D.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
relatedAward
Indicates that there is an award connected or associated with the subject entity, such as an honor, prize, or recognition related to it.
- 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_69a24d4862f881908cc8b89d3a78031d |
completed | Feb. 28, 2026, 2:04 a.m. |
| NER | Named-entity recognition | batch_69a253b95d4c81909d1f2bc37e799c44 |
completed | Feb. 28, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69a24ebfc5a88190bdd1653b9fa541fe |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.