Triple
T14949237
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | aspron trachy |
E372746
|
entity |
| Predicate | mintingTechnique |
P55535
|
FINISHED |
| Object | struck coin |
—
|
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: struck coin | Statement: [aspron trachy, mintingTechnique, struck coin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mintingTechnique Context triple: [aspron trachy, mintingTechnique, struck coin]
-
A.
mintingTechnologyContext
chosen
Indicates the technological method or process used to mint or produce something, typically specifying the context or conditions under which the minting took place.
-
B.
typeOfMint
Indicates that one entity is a specific kind or variety of mint relative to another entity.
-
C.
mintedFrom
Indicates that a newly created token, coin, or digital asset originates from or is derived directly from a specified source asset or input.
-
D.
mintedAt
Indicates the specific time or block at which a digital asset or token was created (minted) on a blockchain.
-
E.
mint
Indicates the act of creating or issuing something new, typically in an official or authoritative capacity (such as producing new currency or tokens).
- 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_69d85cca979481908747d2a81eba1cea |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded68fae3c81909873b113bfcaca05 |
completed | April 15, 2026, 12:06 a.m. |
| PD | Predicate disambiguation | batch_69de9a588c2c8190b1245a1c406f447c |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:39 a.m.