Triple
T31851883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gold yuan |
E813085
|
entity |
| Predicate | monetaryReformPurpose |
P39456
|
FINISHED |
| Object | curb hyperinflation |
—
|
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: curb hyperinflation | Statement: [gold yuan, monetaryReformPurpose, curb hyperinflation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetaryReformPurpose Context triple: [gold yuan, monetaryReformPurpose, curb hyperinflation]
-
A.
monetaryPolicyGoal
Indicates that one entity specifies or represents the target objectives or intended outcomes of another entity’s monetary policy.
-
B.
goalOfReforms
chosen
Indicates that a reform or set of reforms is undertaken with the aim or intended objective of achieving a particular outcome.
-
C.
monetaryFunction
Indicates a relationship where something serves a financial role, such as handling, managing, or affecting money or economic value.
-
D.
monetaryUnionGoal
Indicates that one entity has the objective or aim of forming or participating in a monetary union with another entity.
-
E.
monetaryPolicyChange
Indicates a change in a government or central bank’s monetary policy stance, such as adjusting interest rates, reserve requirements, or money supply.
- 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_69f348eb327881909b4584b925742f6e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b03e438c81909ff3b98edd72ae38 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:51 p.m.