Triple
T15265124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Vasili Alexandrovich of Russia |
E364879
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Vasili |
E101378
|
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: Vasili | Statement: [Prince Vasili Alexandrovich of Russia, givenName, Vasili]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Vasili Context triple: [Prince Vasili Alexandrovich of Russia, givenName, Vasili]
-
A.
Vasily
chosen
Vasily is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
B.
Vsevolod
Vsevolod is a masculine given name of Slavic origin, most notably borne by the influential Russian theatre director Vsevolod Meyerhold.
-
C.
Arseny
Arseny is a masculine given name of Russian origin, historically borne by several notable figures in literature, art, and public life.
-
D.
Zinoviy
Zinoviy is a masculine given name of Slavic origin, commonly used in Russian and Ukrainian contexts.
-
E.
Ignatyev
Ignatyev is a Russian surname borne by various notable figures in politics, military, sports, and the arts.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00851c5b88190a296b6a105d3ee30 |
completed | April 15, 2026, 9:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff8757325c8190ad97f50368862ca5 |
completed | May 9, 2026, 7:13 p.m. |
Created at: April 10, 2026, 3:14 a.m.