Triple
T9123750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosneft |
E218921
|
entity |
| Predicate | hasTickerSymbol |
P1447
|
FINISHED |
| Object | ROSN |
E218921
|
NE 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: ROSN | Statement: [Rosneft, hasTickerSymbol, ROSN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ROSN Context triple: [Rosneft, hasTickerSymbol, ROSN]
-
A.
ROSN
chosen
ROSN is the stock ticker symbol for Rosneft, a major Russian state-controlled oil and gas company.
-
B.
РВСН
РВСН is the Russian abbreviation for the Strategic Missile Forces, the branch of Russia’s armed forces responsible for land-based intercontinental ballistic missiles and nuclear deterrence.
-
C.
Rusk
Rusk is a surname most notably associated with Dean Rusk, who served as United States Secretary of State during the Kennedy and Johnson administrations.
-
D.
Rus'
Rus' was a medieval East Slavic state that emerged in Eastern Europe and laid the foundations for the later Russian, Ukrainian, and Belarusian nations.
-
E.
RU-KOS
RU-KOS is the ISO 3166-2 subdivision code assigned to Kostroma Oblast, a federal subject in central Russia.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8b5fa188190be6465e74cf26915 |
completed | April 1, 2026, 5:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d030988a888190b5a1e4fd6bd7fcee |
completed | April 3, 2026, 9:26 p.m. |
Created at: March 30, 2026, 7:17 p.m.