Triple
T1117397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coinage Act of 1853 |
E11131
|
entity |
| Predicate | changedSilverContentOf |
P25132
|
FINISHED |
| Object | half dime |
—
|
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: half dime | Statement: [Coinage Act of 1853, changedSilverContentOf, half dime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedSilverContentOf Context triple: [Coinage Act of 1853, changedSilverContentOf, half dime]
-
A.
silverContentStandard
Indicates the standard or required amount of silver content specified for something, such as a material, product, or item.
-
B.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
C.
redeemabilityEndedForSilver
Indicates that the ability to redeem silver (e.g., for currency or obligations) has ceased or is no longer valid.
-
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. chosen
Provenance (4 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4562f48190831e959f5f309956 |
completed | March 1, 2026, 10:18 p.m. |
| PDg | Predicate description generation | batch_69a4bc47fce48190825d3a877251f789 |
completed | March 1, 2026, 10:23 p.m. |
Created at: March 1, 2026, 7:43 p.m.