Triple
T57816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bretton Woods system |
E1144
|
entity |
| Predicate | goldPrice |
P482
|
FINISHED |
| Object | 35 U.S. dollars per troy ounce of gold |
—
|
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: 35 U.S. dollars per troy ounce of gold | Statement: [Bretton Woods system, goldPrice, 35 U.S. dollars per troy ounce of gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goldPrice Context triple: [Bretton Woods system, goldPrice, 35 U.S. dollars per troy ounce of gold]
-
A.
definedGoldSilverRatio
Indicates that an entity has established or specified a particular exchange rate or proportional relationship between gold and silver.
-
B.
currency
Indicates that one entity serves as the medium of exchange or monetary unit used by another entity (such as a country, region, or system).
-
C.
authorizedCoinMetal
Indicates that a particular metal is officially approved for use in minting a given coin.
-
D.
market
Indicates the act of promoting, advertising, or selling a product, service, or idea to potential buyers or target audiences.
-
E.
monetaryValue
chosen
Indicates the amount of money associated with an entity, event, or transaction.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b915c9881908c798f4dacb39f1d |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac6799c8190b508933acc0a4c7d |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.