Triple
T20570115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruslan |
E505071
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Rusłan |
—
|
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: Rusłan | Statement: [Ruslan, hasVariant, Rusłan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rusłan Context triple: [Ruslan, hasVariant, Rusłan]
-
A.
Ruslan
chosen
Ruslan is a masculine given name of Turkic origin widely used in Slavic countries, often associated with literary and historical figures.
-
B.
Ilya Muromets
Ilya Muromets is a legendary bogatyr (epic hero) of East Slavic folklore, famed for his superhuman strength, heroic exploits, and central role in Russian byliny (oral epic poems).
-
C.
Gerasim
Gerasim is the compassionate peasant servant in Leo Tolstoy’s novella "The Death of Ivan Ilyich," known for his honesty, simplicity, and humane care for the dying protagonist.
-
D.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
E.
Svyatogor
Svyatogor was a Russian icebreaker later renamed Krasin, notable for its Arctic exploration and rescue missions in the early 20th century.
- 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_69e0b4b721588190993ac7b0a9be2736 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a7a5b0688190b45d0fa993c4765c |
completed | April 20, 2026, 10:24 p.m. |
Created at: April 16, 2026, 11:39 a.m.