Triple
T4322075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morgan dollar |
E96540
|
entity |
| Predicate | silverWeight |
P56222
|
FINISHED |
| Object | 0.77344 troy ounce |
—
|
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.77344 troy ounce | Statement: [Morgan dollar, silverWeight, 0.77344 troy ounce]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: silverWeight Context triple: [Morgan dollar, silverWeight, 0.77344 troy ounce]
-
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.
changedSilverContentOf
Indicates that one entity altered the amount or proportion of silver contained in another entity.
-
D.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
E.
previousGoldPurity
Indicates that one entity represents the gold purity value that applied to another entity at an earlier time or in a prior state.
- 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_69b345422aac81909ddbadae437d122e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3511608dc8190afe912aa605ecace |
completed | March 12, 2026, 11:49 p.m. |
| PD | Predicate disambiguation | batch_69b34f4bec888190987fc2631498b637 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3501834448190bedf775a80da4778 |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:12 p.m.