Triple
T18417889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Silver Eagle |
E441942
|
entity |
| Predicate | purityStandard |
P123823
|
FINISHED |
| Object | 99.9% 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: 99.9% silver | Statement: [American Silver Eagle, purityStandard, 99.9% silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: purityStandard Context triple: [American Silver Eagle, purityStandard, 99.9% silver]
-
A.
purity
Indicates that an entity possesses a high degree of cleanliness, integrity, or freedom from contamination, corruption, or mixed elements.
-
B.
purifiedBy
Indicates that something has been cleansed, refined, or made pure through the action or process performed by another agent or method.
-
C.
standardFineness
chosen
Indicates that one entity conforms to a recognized or prescribed level of fineness or granularity relative to a defined standard.
-
D.
protectionStandard
Indicates that one entity establishes or adheres to a specified level or type of protection for another entity or resource.
-
E.
isStandardOf
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
- 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_69d8b9eb8a508190a942fd75ebd8b1dc |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e51a291f148190b289b5b617077797 |
completed | April 19, 2026, 6:08 p.m. |
| PD | Predicate disambiguation | batch_69e469bf7f74819096a01173493412c2 |
completed | April 19, 2026, 5:35 a.m. |
Created at: April 10, 2026, 10:47 a.m.