Triple
T2525376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bland–Allison Act |
E56021
|
entity |
| Predicate | silverDollarFineness |
P16789
|
FINISHED |
| Object | 0.900 fine silver |
—
|
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: 0.900 fine silver | Statement: [Bland–Allison Act, silverDollarFineness, 0.900 fine silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: silverDollarFineness Context triple: [Bland–Allison Act, silverDollarFineness, 0.900 fine silver]
-
A.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
B.
silverContentStandard
chosen
Indicates the standard or required amount of silver content specified for something, such as a material, product, or item.
-
C.
changedSilverContentOf
Indicates that one entity altered the amount or proportion of silver contained in another entity.
-
D.
previousGoldPurity
Indicates that one entity represents the gold purity value that applied to another entity at an earlier time or in a prior state.
-
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_69ab4a48e4f081908f1218d244608659 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2544b4481908e105294cebdbb1f |
completed | March 7, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.