Triple
T21827926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yevgeni Preobrazhensky |
E538903
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Yevgeni |
—
|
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: Yevgeni | Statement: [Yevgeni Preobrazhensky, givenName, Yevgeni]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yevgeni Context triple: [Yevgeni Preobrazhensky, givenName, Yevgeni]
-
A.
Yevgeny
chosen
Yevgeny is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
B.
Semyon
Semyon is a masculine given name of Russian origin, commonly used in Slavic countries.
-
C.
Anatoly
Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Nikolay
Nikolay is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and equivalent to Nicholas in English.
-
E.
Georgii
Georgii is a masculine given name, commonly used in Slavic countries as a variant of George.
- 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_69e0c475038c8190abb9b1a20eb8ff50 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f09133718081909faa67c3721aed52 |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 16, 2026, 6:54 p.m.