Triple
T5461149
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruslan and Ludmila |
E122595
|
entity |
| Predicate | hasMainCharacter |
P1183
|
FINISHED |
| Object | Ruslan |
E505071
|
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: Ruslan | Statement: [Ruslan and Ludmila, hasMainCharacter, Ruslan]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ruslan Context triple: [Ruslan and Ludmila, hasMainCharacter, Ruslan]
-
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.
Gavril
Gavril is a masculine given name, commonly used in Slavic and Eastern European cultures, that derives from the Hebrew name Gabriel.
-
C.
Vasily
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Oleg
Oleg is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
E.
Rodion
Rodion is a masculine given name of Slavic origin, most notably borne by Soviet military commander Rodion Malinovsky.
- 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_69bd4643f16081908d7f29e08096115a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9201dbfc8190bea22d6ecbc25b3e |
completed | March 20, 2026, 6:29 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf414c39a4819098f2862f3c4594c0 |
completed | March 22, 2026, 1:09 a.m. |
Created at: March 20, 2026, 2:08 p.m.