Triple
T10471439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vasili IV of Russia |
E246931
|
entity |
| Predicate | dynasty |
P1547
|
FINISHED |
| Object | Shuisky |
E259608
|
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: Shuisky | Statement: [Vasili IV of Russia, dynasty, Shuisky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shuisky Context triple: [Vasili IV of Russia, dynasty, Shuisky]
-
A.
Shuisky
chosen
Shuisky is a scheming boyar and political intriguer in Alexander Pushkin’s historical drama and Modest Mussorgsky’s opera "Boris Godunov."
-
B.
Yukhnov
Yukhnov is a small historic town in western Russia known for its location on the Ugra River and its role in regional trade and World War II history.
-
C.
Yuzovka
Yuzovka was the original name of the industrial settlement in eastern Ukraine that later developed into the city of Donetsk.
-
D.
Nikolskoye
Nikolskoye is the main and only permanent settlement on Russia’s remote Commander Islands in the Bering Sea.
-
E.
Nikolskoye
Nikolskoye is a town in northwestern Russia known as part of the Saint Petersburg metropolitan area in Leningrad Oblast.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5094cec788190a485c5c9e7cd024a |
completed | April 7, 2026, 1:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d979fa05d8819087e2167cc9247598 |
completed | April 10, 2026, 10:30 p.m. |
Created at: April 6, 2026, 12:20 p.m.