Triple
T21763918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMOEX |
E537229
|
entity |
| Predicate | exchange |
P9798
|
FINISHED |
| Object | MOEX |
—
|
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: MOEX | Statement: [IMOEX, exchange, MOEX]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MOEX Context triple: [IMOEX, exchange, MOEX]
-
A.
MOEX Russia Index
The MOEX Russia Index is a major benchmark stock market index that tracks the performance of the most liquid and largest companies listed on the Moscow Exchange.
-
B.
IMOEX
IMOEX is the ticker symbol for the MOEX Russia Index, a major benchmark tracking the performance of leading Russian stocks listed on the Moscow Exchange.
-
C.
Moscow Exchange
chosen
Moscow Exchange is Russia’s largest securities and derivatives trading platform, providing markets for equities, bonds, currencies, money market instruments, and commodities.
-
D.
MCX
MCX is the stock ticker symbol for a company listed on the FTSE 250 Index, which comprises mid-cap firms traded on the London Stock Exchange.
-
E.
MCX
MCX is the retail store system of the United States Marine Corps, providing goods and services to Marines, their families, and authorized patrons.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031a8a7f08190a4e50ebc24219585 |
completed | April 28, 2026, 4:03 a.m. |
Created at: April 16, 2026, 6:51 p.m.