Triple
T13577419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eisenhower dollar |
E324323
|
entity |
| Predicate | metalCladding |
P26314
|
FINISHED |
| Object | copper–nickel outer layers |
—
|
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: copper–nickel outer layers | Statement: [Eisenhower dollar, metalCladding, copper–nickel outer layers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metalCladding Context triple: [Eisenhower dollar, metalCladding, copper–nickel outer layers]
-
A.
metalColor
Indicates the color attribute associated specifically with a metal or metallic material.
-
B.
associatedMetal
chosen
Indicates a relationship where one entity is linked or connected to a particular metal, such as by composition, usage, origin, or symbolic association.
-
C.
allMetalConstruction
Indicates that something is constructed entirely or almost entirely from metal components.
-
D.
metalComparedWith
Indicates a comparison being made between two metals in terms of some property, quality, or characteristic.
-
E.
stateMetal
Indicates that an entity is in a metallic state or exhibits properties characteristic of a metal.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb02de1988190af2d473973ecd529 |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.