Triple
T23982859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centenario gold coin |
E604551
|
entity |
| Predicate | mintingResumed |
P154131
|
FINISHED |
| Object | 1943 |
—
|
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: 1943 | Statement: [Centenario gold coin, mintingResumed, 1943]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mintingResumed Context triple: [Centenario gold coin, mintingResumed, 1943]
-
A.
mintedAt
Indicates the specific time or block at which a digital asset or token was created (minted) on a blockchain.
-
B.
typeOfMint
Indicates that one entity is a specific kind or variety of mint relative to another entity.
-
C.
closedAsMint
Indicates that an issue, report, or request was resolved and marked as valid or correct in its original form, without requiring changes.
-
D.
secondMintingPeriodStart
Indicates the point in time when the second minting period for an asset or token begins.
-
E.
mintedUntil
Indicates the time or condition up to which something can be or was produced, issued, or created (e.g., coins, tokens, or similar items).
- F. None of above. chosen
Provenance (4 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_69e29543f40c819087700b7a272afb60 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d2bf02fc8190bebd59f149e0bbfc |
completed | April 29, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:29 p.m.