Triple
T18991736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barber dime |
E464698
|
entity |
| Predicate | rarityExample |
P7075
|
FINISHED |
| Object | 1894-S is one of the great rarities of U.S. coinage |
—
|
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: 1894-S is one of the great rarities of U.S. coinage | Statement: [Barber dime, rarityExample, 1894-S is one of the great rarities of U.S. coinage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rarityExample Context triple: [Barber dime, rarityExample, 1894-S is one of the great rarities of U.S. coinage]
-
A.
rarity
chosen
Indicates how uncommon or infrequently an entity or event occurs relative to others in a given context.
-
B.
rarityReason
Indicates the underlying cause or justification for why something is considered rare.
-
C.
instrumentRarity
Indicates how uncommon or scarce an instrument is relative to others.
-
D.
isRareTypeOf
Indicates that one entity is an uncommon or infrequently occurring subtype or category of another entity.
-
E.
isCollectible
Indicates that an item can be gathered, acquired, or kept, typically as part of a set or collection.
- 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_69d8dd01a56c81909694a128c66b21d7 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d67dee4c8190ac2017ff748ea6aa |
completed | April 20, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f88e0c81908cb20f08bf24cd32 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 12:01 p.m.