Triple
T794276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Point Mint |
E16982
|
entity |
| Predicate | beganCoinProduction |
P17359
|
FINISHED |
| Object | 1970s |
—
|
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: 1970s | Statement: [West Point Mint, beganCoinProduction, 1970s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganCoinProduction Context triple: [West Point Mint, beganCoinProduction, 1970s]
-
A.
openedForCoinage
chosen
Indicates that a facility, system, or process has been made available or activated specifically for the production or issuance of coinage.
-
B.
firstYearOfMintage
Indicates the year in which a coin or similar item was first officially produced or issued.
-
C.
firstRedenominationYear
Indicates the year in which a currency or financial unit was first redenominated (i.e., its face value was officially recalibrated or replaced).
-
D.
firstDeployed
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
-
E.
firstDeployedFor
Indicates that an entity was initially deployed or put into operational use specifically for another entity (such as a project, mission, or organization).
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79b976c819085cd381bbd597ca5 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a510f61881909175d6d8719246cd |
completed | March 1, 2026, 8:44 p.m. |
Created at: March 1, 2026, 7:38 p.m.