Triple
T38634008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azes I |
E937530
|
entity |
| Predicate | coinMetals |
P1838
|
FINISHED |
| Object | 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: silver | Statement: [Azes I, coinMetals, silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinMetals Context triple: [Azes I, coinMetals, silver]
-
A.
authorizedCoinMetal
chosen
Indicates that a particular metal is officially approved for use in minting a given coin.
-
B.
relatedModernBullionCoin
Indicates that there is an association between an entity and a modern bullion coin that is relevant or connected to it in some specific way.
-
C.
nobleMetal
Indicates that the subject is classified as a noble (chemically inert and corrosion-resistant) metal.
-
D.
coinageRarity
Indicates the relative scarcity or commonness of a particular coinage within its issuing context.
-
E.
numismaticField
Indicates that there is a relationship involving the study, collection, or classification of coins, currency, and related monetary objects.
- 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_69f76ed5ca3c81909288f61fbf37b359 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.