Triple
T19182476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sviatoslav II of Kiev |
E469609
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Sviatoslav |
—
|
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: Sviatoslav | Statement: [Sviatoslav II of Kiev, givenName, Sviatoslav]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sviatoslav Context triple: [Sviatoslav II of Kiev, givenName, Sviatoslav]
-
A.
Sviatoslav
chosen
Sviatoslav is a masculine given name of Slavic origin, historically borne by medieval rulers such as Sviatoslav I of Kiev.
-
B.
Oleg
Oleg is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
C.
Roman Sviatoslavich
Roman Sviatoslavich was a medieval Rus' prince from the Sviatoslavichi dynasty of Chernigov, active in the complex dynastic and territorial politics of Kievan Rus'.
-
D.
Yaroslav
Yaroslav is a given name of Slavic origin, commonly used in Eastern Europe and associated with several historical rulers and notable figures.
-
E.
Vsevolod
Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f61cab348190965e96ac0f701f9f |
completed | April 20, 2026, 9:47 a.m. |
Created at: April 10, 2026, 12:07 p.m.