Triple

T1427787
Position Surface form Disambiguated ID Type / Status
Subject S&P 500 ETFs E30371 entity
Predicate underlyingIndexType P19875 FINISHED
Object market-cap-weighted index 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: market-cap-weighted index | Statement: [S&P 500 ETFs, underlyingIndexType, market-cap-weighted index]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: underlyingIndexType
Context triple: [S&P 500 ETFs, underlyingIndexType, market-cap-weighted index]
  • A. indexType chosen
    Indicates the classification or category of an index associated with an entity or structure.
  • B. associatedIndex
    Indicates that one entity is linked to another through a corresponding index or positional reference.
  • C. offsetType
    Indicates the specific kind or category of offset applied in a relationship, such as how far or in what manner one value, position, or event is shifted relative to another.
  • D. hasBaseIndex
    Indicates that one entity serves as the reference or starting index from which another entity’s position, offset, or ordering is calculated.
  • E. underlyingInstrument
    Indicates that one financial instrument serves as the reference or basis for the value, payoff, or structure of another financial instrument.
  • 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_69a498fb823c8190a67ce4c4837e641a completed March 1, 2026, 7:52 p.m.
NER Named-entity recognition batch_69a4c52e4ed881908d85e0cb9fe851ac completed March 1, 2026, 11:01 p.m.
PD Predicate disambiguation batch_69a4c4752abc8190a33b634c4d6fad28 completed March 1, 2026, 10:57 p.m.
Created at: March 1, 2026, 8 p.m.