Triple

T25217939
Position Surface form Disambiguated ID Type / Status
Subject VIX futures E631877 entity
Predicate settlementExchange P158037 FINISHED
Object Cboe Futures Exchange 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: Cboe Futures Exchange | Statement: [VIX futures, settlementExchange, Cboe Futures Exchange]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: settlementExchange
Context triple: [VIX futures, settlementExchange, Cboe Futures Exchange]
  • A. isSettlementOf
    Indicates that one entity is a settlement (such as a town, village, or city) that belongs to, is located within, or is administratively part of another entity.
  • B. settlementVenue
    Indicates the place or institution where a settlement (such as a legal, financial, or dispute resolution agreement) is formally carried out or finalized.
  • C. isSettlement
    Indicates that the subject entity functions as a human-inhabited place or community, such as a town, village, or city.
  • D. hasSettlementCurrency
    Indicates that a financial transaction, contract, or account is settled using a specified currency.
  • E. settlementWith
    Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
  • 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_69e75a8d1aa48190a4320acd3654762c completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f47b907f6081908c6c0e33f4cae736 completed May 1, 2026, 10:08 a.m.
PD Predicate disambiguation batch_69f44d849e7c81909945438f40e35362 completed May 1, 2026, 6:51 a.m.
PDg Predicate description generation batch_69f45300bd488190bb1d4160f5534ef6 completed May 1, 2026, 7:15 a.m.
Created at: April 21, 2026, 12:59 p.m.