Triple
T2231046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sherman Silver Purchase Act of 1890 |
E48764
|
entity |
| Predicate | treasuryNotesRedeemableIn |
P7021
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [Sherman Silver Purchase Act of 1890, treasuryNotesRedeemableIn, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treasuryNotesRedeemableIn Context triple: [Sherman Silver Purchase Act of 1890, treasuryNotesRedeemableIn, gold]
-
A.
redeemableAt
chosen
Indicates that something (such as a voucher, coupon, or credit) can be exchanged for value or benefits at a specified place, platform, or entity.
-
B.
notRedeemableFor
Indicates that something cannot be exchanged, converted, or used to obtain another specified item, service, or benefit.
-
C.
legalTenderSince
Indicates the point in time from which something has officially held the status of legal tender within a given jurisdiction.
-
D.
legalTenderUntil
Indicates that a form of money is officially recognized as valid payment only up to a specified date or time.
-
E.
hasBanknotes
Indicates that an entity possesses or contains one or more banknotes.
- 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_69a88aa51b388190949868ec9766e587 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc06b7374819089fe643e12797bfd |
completed | March 7, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69abbdadbb0c8190b3a1ede31b8acbfa |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.