Triple
T4449168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Eagle palladium bullion coin |
E96364
|
entity |
| Predicate | designSource |
P4831
|
FINISHED |
| Object | classic American coin designs |
—
|
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: classic American coin designs | Statement: [American Eagle palladium bullion coin, designSource, classic American coin designs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designSource Context triple: [American Eagle palladium bullion coin, designSource, classic American coin designs]
-
A.
designUse
chosen
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
B.
materialSource
Indicates that one entity serves as the origin or provider of the material or substance used by another entity.
-
C.
designBureau
Indicates that an entity functions as a design bureau responsible for planning, developing, or engineering designs for another entity or project.
-
D.
designedIn
Indicates that something was created, planned, or conceived during a particular time period or at a specific location.
-
E.
designMedium
Indicates the medium or material through which a design is created, expressed, or executed.
- 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_69b345415ba481908df738e7174448ba |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b355d5975c8190bfe8a2d5d2dbf075 |
completed | March 13, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69b34f62c180819097ced38da2052207 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:32 p.m.