Triple
T35918088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Presidential $1 Coin Program |
E1038799
|
entity |
| Predicate | circulationStatusChangeYear |
P149349
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Presidential $1 Coin Program, circulationStatusChangeYear, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circulationStatusChangeYear Context triple: [Presidential $1 Coin Program, circulationStatusChangeYear, 2012]
-
A.
circulationStatus
Indicates the current availability or loan state of an item within a circulation or lending system.
-
B.
circulationPeriod
Indicates the length of time during which an item is allowed to be borrowed, used, or remain in active circulation before it must be returned, renewed, or retired.
-
C.
changedInYear
chosen
Indicates that an entity underwent a change or modification during a specified calendar year.
-
D.
circulationStart
Indicates the point in time or event when the circulation or distribution of something (such as an item, resource, or document) begins.
-
E.
cityStatusYear
Indicates the year in which a place obtained, changed, or was recognized with a particular city status.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:07 p.m.