Triple
T4436903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Eagle platinum bullion coins |
E95672
|
entity |
| Predicate | mintMarkLocation |
P11667
|
FINISHED |
| Object | varies by mint and issue |
—
|
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: varies by mint and issue | Statement: [American Eagle platinum bullion coins, mintMarkLocation, varies by mint and issue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mintMarkLocation Context triple: [American Eagle platinum bullion coins, mintMarkLocation, varies by mint and issue]
-
A.
mintLocations
chosen
Indicates the locations where something is minted, such as coins, tokens, or other items produced through a minting process.
-
B.
mintMarkUsedOn
Indicates that a particular mint mark was applied to or appears on a specific coin or numismatic item.
-
C.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
D.
labelLocation
Indicates that a label or identifier is associated with a specific spatial or geographic location.
-
E.
marksBoundaryIn
Indicates that one entity serves as a boundary or delimiter within, or for a specific region or structure of, another entity.
- 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_69b3453ea2b48190a26f154b3b8fece5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3558b1d4481909060ede5e0ded4bc |
completed | March 13, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69b34f6078cc8190831b89f404198cc5 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:31 p.m.