Triple
T16774186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achaemenid coinage system |
E407679
|
entity |
| Predicate | coreSilverCoin |
P16789
|
FINISHED |
| Object | siglos |
—
|
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: siglos | Statement: [Achaemenid coinage system, coreSilverCoin, siglos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreSilverCoin Context triple: [Achaemenid coinage system, coreSilverCoin, siglos]
-
A.
coinagePower
Indicates the authority or capacity of an entity to create, issue, or regulate currency or coinage.
-
B.
scriptUsedOnCoins
Indicates that a particular writing system or script is used on the inscriptions appearing on coins.
-
C.
keyCoin
Indicates a relationship where one entity functions as a key or primary token granting access, control, or validation in association with another entity.
-
D.
coinageFeature
Indicates a characteristic, design element, or attribute that is present on or associated with a particular coin or type of coinage.
-
E.
silverContentStandard
chosen
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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b038d0608190be15c758427bb664 |
completed | April 18, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.