Triple
T94391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coinage Act of 1834 |
E1896
|
entity |
| Predicate | changedGoldSilverRatioTo |
P1835
|
FINISHED |
| Object | approximately 16:1 |
—
|
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: approximately 16:1 | Statement: [Coinage Act of 1834, changedGoldSilverRatioTo, approximately 16:1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedGoldSilverRatioTo Context triple: [Coinage Act of 1834, changedGoldSilverRatioTo, approximately 16:1]
-
A.
definedGoldSilverRatio
chosen
Indicates that an entity has established or specified a particular exchange rate or proportional relationship between gold and silver.
-
B.
replacedCurrency
Indicates that one currency has been superseded and no longer used because another currency has taken its place.
-
C.
replacedCurrencyRate
Indicates that one currency exchange rate has been superseded or substituted by another rate in a given context.
-
D.
formerCurrency
Indicates that an entity was once used as a currency in a place or time period but is no longer in official use.
-
E.
authorizedCoinMetal
Indicates that a particular metal is officially approved for use in minting a given coin.
- 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_69a24feef1b08190bb9525f71cce053e |
completed | Feb. 28, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69a24ebb3da08190a8b82564f33cde3b |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:09 a.m.