Triple
T7795058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roosevelt dime |
E180277
|
entity |
| Predicate | metalContentPre1965 |
P79068
|
FINISHED |
| Object | 90% 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: 90% silver | Statement: [Roosevelt dime, metalContentPre1965, 90% silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metalContentPre1965 Context triple: [Roosevelt dime, metalContentPre1965, 90% silver]
-
A.
legalTenderStatusAfter1933
Indicates whether something retained or acquired the status of legal tender following the monetary and legal changes implemented after the year 1933.
-
B.
coinageDate
Indicates the date or time period when a coin (or currency unit) was first minted or officially issued.
-
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.
coinsProduced
Indicates that a particular entity (such as a mint or authority) has produced or issued a specified set or quantity of coins.
- 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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
| PDg | Predicate description generation | batch_69caf7855a3c81908b9318f7186fc0c0 |
completed | March 30, 2026, 10:21 p.m. |
Created at: March 30, 2026, 4:31 p.m.