Triple
T13577441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eisenhower dollar |
E324323
|
entity |
| Predicate | standardCirculationComposition |
P8601
|
FINISHED |
| Object | copper–nickel clad |
—
|
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 clad | Statement: [Eisenhower dollar, standardCirculationComposition, copper–nickel clad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardCirculationComposition Context triple: [Eisenhower dollar, standardCirculationComposition, copper–nickel clad]
-
A.
standardComposition
chosen
Indicates that one entity is composed or constructed according to a recognized or conventional standard defined by another entity.
-
B.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
C.
standardWithin
Indicates that one entity conforms to, or falls within the limits of, a specified standard defined by another entity.
-
D.
standardType
Indicates that one entity is classified as the standard, canonical, or reference type for another entity or context.
-
E.
standardCreated
Indicates that an entity is responsible for the creation or establishment of a particular standard.
- 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.