Triple
T1686426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail |
E36451
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Mikhayil |
E36451
|
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: Mikhayil | Statement: [Mikhail, hasVariant, Mikhayil]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mikhayil Context triple: [Mikhail, hasVariant, Mikhayil]
-
A.
Mikhail
chosen
Mikhail is a common Russian male given name, famously borne by Soviet leader Mikhail Gorbachev.
-
B.
Semyon
Semyon is a masculine given name of Russian origin, commonly used in Slavic countries.
-
C.
Mikhail Mil
Mikhail Mil was a Soviet aerospace engineer and helicopter designer best known as the founder and chief designer of the Mil Moscow Helicopter Plant, which produced many of the USSR’s most important rotorcraft.
-
D.
Vyacheslav
Vyacheslav is a masculine given name of Slavic origin, most notably borne by Soviet politician Vyacheslav Molotov.
-
E.
Leonid
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa6293c368819094ab0f615e418647 |
completed | March 6, 2026, 5:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69afe85a92fc8190b9218c499fb08bfe |
completed | March 10, 2026, 9:46 a.m. |
Created at: March 4, 2026, 7:29 p.m.