Triple
T25217930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIX futures |
E631877
|
entity |
| Predicate | tickerExample |
P81722
|
FINISHED |
| Object | VX |
—
|
NE NERFINISHED |
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: VX | Statement: [VIX futures, tickerExample, VX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tickerExample Context triple: [VIX futures, tickerExample, VX]
-
A.
tickerFor
Indicates that one entity is the stock ticker symbol used to uniquely identify another entity (typically a publicly traded company or security) in financial markets.
-
B.
tickerSymbol
Indicates the association between a financial instrument or company and its unique abbreviated code used for trading on a securities exchange.
-
C.
indicatorExample
chosen
Indicates that one entity serves as an example or instance illustrating the characteristics, behavior, or usage of another entity.
-
D.
overseesTicker
Indicates that one entity has supervisory or managerial responsibility over the activities or status associated with a specific ticker symbol.
-
E.
economicTrackExample
Indicates a relationship where one entity serves as an illustrative or representative example of another entity’s economic trajectory, path, or development.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5ffc74fa481909b4fe24a9337f9eb |
completed | May 2, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69f5f7f99dc08190afcfb3bc4dfbec1d |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 21, 2026, 12:59 p.m.