Triple
T31851884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gold yuan |
E813085
|
entity |
| Predicate | monetaryReformOutcome |
P81058
|
FINISHED |
| Object | unsuccessful |
—
|
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: unsuccessful | Statement: [gold yuan, monetaryReformOutcome, unsuccessful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetaryReformOutcome Context triple: [gold yuan, monetaryReformOutcome, unsuccessful]
-
A.
successorMonetarySystem
Indicates that one monetary system directly follows and replaces another in time or function.
-
B.
typeOfCoinageReform
Indicates a relationship where a specific reform is classified by the particular type or category of coinage reform it represents.
-
C.
denominationReform
Indicates a change or restructuring in a religious denomination’s doctrines, practices, or organizational form.
-
D.
economicPolicyOutcome
chosen
Indicates the resulting economic conditions, effects, or consequences that arise from implementing a particular economic policy.
-
E.
reintroducedCurrencyOf
Indicates that a currency has been brought back into use as legal tender in a particular country or region after having been previously replaced, discontinued, or suspended.
- 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_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 30, 2026, 11:51 p.m.