Triple
T36190132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittman Act of 1918 |
E1046962
|
entity |
| Predicate | affectedCurrency |
P4256
|
FINISHED |
| Object | Morgan silver dollar |
—
|
NE NERFINISHED |
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: Morgan silver dollar | Statement: [Pittman Act of 1918, affectedCurrency, Morgan silver dollar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedCurrency Context triple: [Pittman Act of 1918, affectedCurrency, Morgan silver dollar]
-
A.
currencyInfluence
Indicates how one currency affects the value, stability, or behavior of another currency or an economic system.
-
B.
influencedCurrencyName
Indicates that one currency has affected or shaped the value, status, or characteristics of another currency.
-
C.
issuesCurrency
Indicates that an entity has the authority to create and put a specific currency into official circulation.
-
D.
replacedCurrency
Indicates that one currency has been superseded and no longer used because another currency has taken its place.
-
E.
involvesCurrency
chosen
Indicates that the relationship or action includes or pertains to the use, exchange, or specification of a particular currency.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:08 p.m.