Triple
T5824197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Treasury futures |
E129181
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interest rate derivative |
C4205
|
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: interest rate derivative Context triple: [U.S. Treasury futures, instanceOf, interest rate derivative]
-
A.
financial derivative
A financial derivative is a contract whose value is based on the performance of an underlying asset, index, rate, or other financial variable, used for hedging risk, speculation, or arbitrage.
-
B.
interest rate futures contract
chosen
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.
-
C.
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.
-
D.
interest rate benchmark
An interest rate benchmark is a standardized reference rate, typically derived from the average rates at which major financial institutions lend to one another, used to set or compare interest rates on various financial products and contracts.
-
E.
financial instrument
A financial instrument is a tradable asset or contract that represents a legal agreement involving monetary value, such as stocks, bonds, derivatives, or loans.
- 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_69c00849d55481908b4f9f5543e0bf6d |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:53 p.m.