Triple
T3741026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coinage Act of 1835 |
E79696
|
entity |
| Predicate | authorizedMintFunction |
P19211
|
FINISHED |
| Object | coinage of gold |
—
|
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: coinage of gold | Statement: [Coinage Act of 1835, authorizedMintFunction, coinage of gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorizedMintFunction Context triple: [Coinage Act of 1835, authorizedMintFunction, coinage of gold]
-
A.
mintStatusGranted
chosen
Indicates that an entity has been officially authorized or approved to mint (create or issue) something, such as tokens, assets, or items.
-
B.
mintedAt
Indicates the specific time or block at which a digital asset or token was created (minted) on a blockchain.
-
C.
reasonForMintLocation
Indicates that the specified location is the place where something (typically currency or tokens) is created or issued.
-
D.
closedAsMint
Indicates that an issue, report, or request was resolved and marked as valid or correct in its original form, without requiring changes.
-
E.
maxSupply
Indicates the maximum quantity of a resource, asset, or token that can ever be created or made available.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb549490819084ebe69aae5ccf95 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.