Triple
T7795060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roosevelt dime |
E180277
|
entity |
| Predicate | metalContentPost1965 |
P1838
|
FINISHED |
| Object | copper-nickel clad |
—
|
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: copper-nickel clad | Statement: [Roosevelt dime, metalContentPost1965, copper-nickel clad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metalContentPost1965 Context triple: [Roosevelt dime, metalContentPost1965, copper-nickel clad]
-
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.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
C.
authorizedCoinMetal
chosen
Indicates that a particular metal is officially approved for use in minting a given coin.
-
D.
coinageDate
Indicates the date or time period when a coin (or currency unit) was first minted or officially issued.
-
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.
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_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. |
Created at: March 30, 2026, 4:31 p.m.