Triple
T20710621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail Alekseyev |
E509026
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Alekseyev |
—
|
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: Alekseyev | Statement: [Mikhail Alekseyev, familyName, Alekseyev]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alekseyev Context triple: [Mikhail Alekseyev, familyName, Alekseyev]
-
A.
Alekseyev
chosen
Alekseyev is a Russian surname borne by various notable figures in Russian history, military, and culture.
-
B.
Vasilyev
Vasilyev is a common Russian surname typically used in its masculine form.
-
C.
Goryachev
Goryachev is a Russian surname, typically the masculine form from which the feminine variant "Goryacheva" is derived.
-
D.
Shchusev
Shchusev is a Russian surname most notably associated with Alexey Shchusev, a prominent Soviet architect known for designing Lenin's Mausoleum in Moscow.
-
E.
Semyonov
Semyonov is a common Russian surname borne by numerous notable figures in fields such as literature, science, and military history.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1974ba08190b0e5ad529be95e4c |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 12:14 p.m.