Triple
T3524666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago SRW wheat |
E74508
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | futures contract underlying |
C4217
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: futures contract underlying Context triple: [Chicago SRW wheat, instanceOf, futures contract underlying]
-
A.
futures contract
A futures contract is a standardized legal agreement traded on an exchange to buy or sell a specific asset at a predetermined price on a set future date.
-
B.
futures contract category
chosen
A futures contract category is a classification grouping standardized futures contracts based on shared underlying assets or market characteristics, such as commodities, currencies, interest rates, or equity indexes.
-
C.
interest rate futures contract
An interest rate futures contract is a standardized, exchange-traded agreement to buy or sell a specified debt instrument or interest rate index at a predetermined price on a future date, used primarily to hedge or speculate on interest rate movements.
-
D.
cash-settled futures
A cash-settled futures is a standardized derivative contract in which, at expiration, the parties settle the difference between the contract price and the underlying asset’s market price in cash rather than delivering the physical asset.
-
E.
exchange-traded derivative
An exchange-traded derivative is a standardized financial contract, such as a futures or options contract, that is bought and sold on a regulated exchange and whose value is derived from an underlying asset, index, or rate.
- F. None of above.
Provenance (1 batch)
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_69ad85d0c5488190a3d8e02ebd01a1aa |
completed | March 8, 2026, 2:21 p.m. |
Created at: March 8, 2026, 3:19 p.m.