Triple

T21002189
Position Surface form Disambiguated ID Type / Status
Subject RTSI E517320 entity
Predicate alsoKnownAs P39 FINISHED
Object RTS Index 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: RTS Index | Statement: [RTSI, alsoKnownAs, RTS Index]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RTS Index
Context triple: [RTSI, alsoKnownAs, RTS Index]
  • A. RTS Index chosen
    RTS Index is a major Russian stock market index that tracks the performance of leading companies listed on the Moscow Exchange, calculated in US dollars.
  • B. RTSI
    RTSI is the commonly used abbreviation for the RTS Index, a benchmark stock market index tracking major companies listed on the Moscow Exchange.
  • C. RTS
    RTS is a major Russian securities exchange that facilitates trading in stocks, bonds, and other financial instruments.
  • D. RTS
    RTS is the commonly used abbreviation for Widzew Łódź, a historic Polish football club based in Łódź.
  • E. RTS
    RTS is the IATA airport code for Rottnest Island Airport, a small regional airport serving Rottnest Island off the coast of Western Australia.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b5006e2881909fc2383f841740cc completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e6fc38b8688190860fba1b58e1b3e6 completed April 21, 2026, 4:25 a.m.
Created at: April 16, 2026, 1:52 p.m.