Triple
T595607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fed funds futures |
E17374
|
entity |
| Predicate | maturityRange |
P15878
|
FINISHED |
| Object | monthly contracts |
—
|
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: monthly contracts | Statement: [Fed funds futures, maturityRange, monthly contracts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maturityRange Context triple: [Fed funds futures, maturityRange, monthly contracts]
-
A.
servesAgeRange
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
D.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
E.
hasAdultRank
Indicates that an entity holds a status or position classified as an adult-level rank within a given system or hierarchy.
- 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.