Triple
T22707159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Andreievich |
E561485
|
entity |
| Predicate | hasVariantTransliteration |
P5923
|
FINISHED |
| Object | Andreevich |
—
|
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: Andreevich | Statement: [Andreievich, hasVariantTransliteration, Andreevich]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Andreevich Context triple: [Andreievich, hasVariantTransliteration, Andreevich]
-
A.
Andreievich
chosen
Andreievich is a Russian patronymic indicating that a man is the son of someone named Andrei.
-
B.
Alexandrovich
Alexandrovich is the Russian patronymic indicating "son of Alexander," famously used in the full name of Tsar Nicholas II of Russia.
-
C.
Arkadyevich
Arkadyevich is the patronymic of Stepan Arkadyevich Oblonsky, a central socialite and bureaucratic character in Leo Tolstoy’s novel "Anna Karenina."
-
D.
Alekseevich
Alekseevich is a Russian patronymic surname or middle name derived from the given name Aleksey, indicating "son of Aleksey."
-
E.
Eduardovich
Eduardovich is a Russian patronymic derived from the given name Eduard, traditionally used as the middle name indicating "son of Eduard."
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178cff7588190a40c8cef0f3cd44a |
completed | April 29, 2026, 3:19 a.m. |
Created at: April 17, 2026, 3:17 p.m.