Triple
T595574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-mini S&P 500 futures |
E17373
|
entity |
| Predicate | liquidity |
P6188
|
FINISHED |
| Object | highly liquid futures contract |
—
|
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: highly liquid futures contract | Statement: [E-mini S&P 500 futures, liquidity, highly liquid futures contract]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liquidity Context triple: [E-mini S&P 500 futures, liquidity, highly liquid futures contract]
-
A.
funds
Indicates that one entity provides financial resources or monetary support to another entity or activity.
-
B.
convertibility
Indicates the capacity or possibility for one entity, state, or form to be changed or transformed into another.
-
C.
flowType
Indicates the kind or category of flow (such as direction, pattern, or mode of movement/transfer) that characterizes the relationship between entities.
-
D.
availability
Indicates that an entity is present, accessible, or ready for use or interaction by another entity.
-
E.
isWidelyTraded
chosen
Indicates that an asset or item is frequently bought and sold across many participants or markets, resulting in high trading activity and liquidity.
- 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.