Triple

T25070563
Position Surface form Disambiguated ID Type / Status
Subject SPE350 E627894 entity
Predicate hasIndexUniverse P147509 FINISHED
Object European large and mid-cap stocks via S&P Europe 350 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: European large and mid-cap stocks via S&P Europe 350 | Statement: [SPE350, hasIndexUniverse, European large and mid-cap stocks via S&P Europe 350]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasIndexUniverse
Context triple: [SPE350, hasIndexUniverse, European large and mid-cap stocks via S&P Europe 350]
  • A. hasIndex
    Indicates that one entity serves as an index or positional reference for another entity within an ordered collection or structure.
  • B. hasIndexSet
    Indicates that something is associated with, defined over, or organized according to a particular set of indices.
  • C. hasIndexing
    Indicates that one entity organizes, catalogs, or references another entity using an index or indexing system.
  • D. hasIndexProvider
    Indicates that an entity is associated with or uses a specific index provider responsible for supplying indexing capabilities or services.
  • E. hasIndexMembership chosen
    Indicates that an entity is included as a member or constituent within a specified index or indexed collection.
  • 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_69e2ff2d71dc8190b4758e57d643cbe4 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f65f7731e4819099d5bd3d915ee266 completed May 2, 2026, 8:32 p.m.
PD Predicate disambiguation batch_69f65c1f94ac8190bc6fbc7916fc0d82 completed May 2, 2026, 8:18 p.m.
Created at: April 18, 2026, 6:10 a.m.