Triple
T32099736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yehud coinage |
E819810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ancient coinage |
C61358
|
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: ancient coinage Context triple: [Yehud coinage, instanceOf, ancient coinage]
-
A.
historical coin
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.
-
B.
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.
-
C.
copper coinage
Copper coinage refers to money in the form of coins primarily composed of copper or copper-based alloys, historically used for low-denomination transactions due to the metal’s relative abundance and low intrinsic value.
-
D.
Achaemenid coin
An Achaemenid coin is a piece of ancient currency issued by the Achaemenid Persian Empire, typically featuring royal iconography and inscriptions that reflect the empire’s political authority and economic system.
-
E.
coinage metal
A coinage metal is a metallic element, typically copper, silver, or gold, valued for its durability, resistance to corrosion, and workability, making it suitable for minting coins.
- F. None of above. chosen
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_69f34901106881908ea893ad504a08be |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:26 a.m.