Triple
T5642668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOEX Russia Index |
E124304
|
entity |
| Predicate | isMajorBenchmarkFor |
P23745
|
FINISHED |
| Object | Russian equities |
—
|
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: Russian equities | Statement: [MOEX Russia Index, isMajorBenchmarkFor, Russian equities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMajorBenchmarkFor Context triple: [MOEX Russia Index, isMajorBenchmarkFor, Russian equities]
-
A.
primaryBenchmarkProvider
Indicates that one entity serves as the main or default source of benchmark data or performance standards for another entity.
-
B.
benchmarkFor
chosen
Indicates that one entity serves as a standard or reference point against which the performance, quality, or characteristics of another entity are measured or evaluated.
-
C.
isMajor
Indicates that an entity holds primary or greater significance, importance, or rank relative to others in a given context.
-
D.
isMajorBaseIn
Indicates that a location serves as a primary or central base of operations within a specified area or organization.
-
E.
isMajorPeakOf
Indicates that one peak is a primary or most prominent summit within a specified mountain, range, or geographic area.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a6a22881908d16f4df564ed2a2 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.