Triple
T7484992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. commemorative coin programs |
E176858
|
entity |
| Predicate | modernEraStart |
P76510
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [U.S. commemorative coin programs, modernEraStart, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernEraStart Context triple: [U.S. commemorative coin programs, modernEraStart, 1982]
-
A.
modernizationPeriod
Indicates the time span during which an entity undergoes or is subject to modernization efforts or processes.
-
B.
numberInModernEra
Indicates that the associated number or count applies specifically to the modern era timeframe, as opposed to historical or earlier periods.
-
C.
modernUse
Indicates how something is currently used or applied in modern times.
-
D.
historicalEraUsheredIn
Indicates the historical era or period that was initiated or brought about as a result of a particular event, action, or entity.
-
E.
modernEquivalent
Indicates that one entity serves as the contemporary or updated counterpart of another earlier or traditional entity.
- F. None of above. chosen
Provenance (4 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f53a6bc081909f4b9cd7cdacf045 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f105e320819091db3cdb1f1351f0 |
completed | March 27, 2026, 9:05 p.m. |
Created at: March 27, 2026, 3:42 p.m.