Triple
T4404055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Eagle gold bullion coin |
E93684
|
entity |
| Predicate | goldPurity |
P14349
|
FINISHED |
| Object | 22 karat |
—
|
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: 22 karat | Statement: [American Eagle gold bullion coin, goldPurity, 22 karat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goldPurity Context triple: [American Eagle gold bullion coin, goldPurity, 22 karat]
-
A.
previousGoldPurity
Indicates that one entity represents the gold purity value that applied to another entity at an earlier time or in a prior state.
-
B.
standardGoldContent
chosen
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
C.
associatedMetal
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
D.
changedSilverContentOf
Indicates that one entity altered the amount or proportion of silver contained in another entity.
-
E.
silverContentStandard
Indicates the standard or required amount of silver content specified for something, such as a material, product, or item.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b352d1af608190ac06d50433cf24bb |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.