Triple
T595623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fed funds futures |
E17374
|
entity |
| Predicate | priceInfluencedBy |
P15880
|
FINISHED |
| Object | U.S. macroeconomic data releases |
—
|
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: U.S. macroeconomic data releases | Statement: [Fed funds futures, priceInfluencedBy, U.S. macroeconomic data releases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: priceInfluencedBy Context triple: [Fed funds futures, priceInfluencedBy, U.S. macroeconomic data releases]
-
A.
relativePrice
Indicates a comparison of the cost or monetary value of one entity relative to another.
-
B.
purchasePrice
Indicates the monetary amount paid or agreed to be paid to acquire something in a purchase transaction.
-
C.
isPriceIndex
Indicates that a value represents a price index, expressing the relative level or change of prices compared to a reference point or period.
-
D.
pricingStrategy
Indicates the approach or method used to set, adjust, or structure prices for products or services in a given context.
-
E.
acquisitionPrice
Indicates the monetary amount paid to acquire an asset, company, or item in a transaction.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a4985b7d7481909b5d30f4001ed61c |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:33 p.m.