Triple
T595658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CME Ether futures |
E17375
|
entity |
| Predicate | settlementCurrency |
P12372
|
FINISHED |
| Object | USD |
—
|
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: USD | Statement: [CME Ether futures, settlementCurrency, USD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settlementCurrency Context triple: [CME Ether futures, settlementCurrency, USD]
-
A.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
-
B.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
C.
associatedCurrencyCode
chosen
Indicates the currency code that is linked to or used in connection with the given entity or transaction.
-
D.
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).
-
E.
currencyPlanned
Indicates that a specific currency is intended or scheduled to be used in a planned transaction, budget, or financial arrangement.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bd280ac8190b6a530ce73da85c8 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494ceeb7881909a91ed1a35d5bf0a |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.