Triple
T4027502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | daric |
E83626
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Achaemenid imperial coinage |
C8587
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Achaemenid imperial coinage Context triple: [daric, instanceOf, Achaemenid imperial coinage]
-
A.
Achaemenid inscription
An Achaemenid inscription is a formal text carved or written on durable materials during the Achaemenid Empire, typically in multiple languages and scripts, to record royal proclamations, commemorations, or religious dedications.
-
B.
Achaemenid noble
An Achaemenid noble is a high-ranking member of the Persian aristocracy who held land, military command, and administrative authority under the Achaemenid Empire, often serving as a close supporter and regional representative of the Great King.
-
C.
Seleucid king
A Seleucid king is a Hellenistic monarch who ruled parts of the former Alexandrian empire in the Near East under the Seleucid dynasty, exercising military, administrative, and cultural authority over a diverse, multiethnic realm.
-
D.
historical coin
chosen
A historical coin is a piece of currency from a past era whose physical characteristics, inscriptions, and context of use provide insight into the economic, political, and cultural history of the society that produced it.
-
E.
historical coin
A historical coin is a minted piece of currency from a past era whose physical characteristics, inscriptions, and context of use provide insight into the economic, political, and cultural history of its time.
- F. None of above.
Provenance (1 batch)
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_69aed92e29ac819080f7a98b594fec05 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:36 p.m.