Triple
T595677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CME Ether futures |
E17375
|
entity |
| Predicate | supportsStrategy |
P13064
|
FINISHED |
| Object | calendar spreads in Ether futures |
—
|
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: calendar spreads in Ether futures | Statement: [CME Ether futures, supportsStrategy, calendar spreads in Ether futures]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStrategy Context triple: [CME Ether futures, supportsStrategy, calendar spreads in Ether futures]
-
A.
usesStrategy
chosen
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
B.
supportsPolicy
Indicates that one entity endorses, backs, or is in favor of a particular policy or set of policies.
-
C.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
D.
supportsPrinciple
Indicates that one entity endorses, upholds, or actively backs a particular principle or doctrine.
-
E.
supportsTheory
Indicates that one entity provides evidence, justification, or endorsement for the validity or acceptance of another entity’s theory.
- 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.