Triple
T13605937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergiy |
E325060
|
entity |
| Predicate | isOftenRomanizedFrom |
P2508
|
FINISHED |
| Object | Сергей |
E64229
|
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: Сергей | Statement: [Sergiy, isOftenRomanizedFrom, Сергей]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Сергей Context triple: [Sergiy, isOftenRomanizedFrom, Сергей]
-
A.
Sergei
chosen
Sergei is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
B.
Юрий
Юрий is a common Russian male given name, often rendered in English as Yuri and borne by numerous notable figures in Russian and Soviet history and culture.
-
C.
Ivan Sergei
Ivan Sergei is an American actor known for his work in film and television, including prominent roles in late-1990s and early-2000s romantic comedies and dramas.
-
D.
Sergeevich
Sergeevich is a Russian patronymic given name indicating descent from a father named Sergei.
-
E.
Alexey
Alexey is a masculine given name of Slavic origin, commonly used in Russian-speaking countries and derived from the Greek name Alexios, meaning "defender" or "helper."
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbe99ddc08190a8d79107c8e176fa |
completed | April 12, 2026, 3:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd3cfae6bc8190ac6851a3fa2dfb12 |
completed | May 8, 2026, 1:31 a.m. |
Created at: April 9, 2026, 9:50 p.m.