Triple
T15352065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhail Shumilov |
E367077
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Shumilov |
E367077
|
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: Shumilov | Statement: [Mikhail Shumilov, familyName, Shumilov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Shumilov Context triple: [Mikhail Shumilov, familyName, Shumilov]
-
A.
Shumilov
chosen
Shumilov is a Russian-language surname borne by various individuals, including military figures and public personalities.
-
B.
Bezymianny
Bezymianny is an active stratovolcano on Russia’s Kamchatka Peninsula, known for its catastrophic 1956 eruption and ongoing explosive activity.
-
C.
Khovrino
Khovrino is a Moscow Metro station serving as the northern terminus of the Zamoskvoretskaya Line.
-
D.
Sulimov
Sulimov was the former name of the city now known as Cherkessk, the capital of Karachay-Cherkessia in southwestern Russia.
-
E.
Kozlov
Kozlov is a historic Russian town, now known as Michurinsk, that developed as a significant regional center of trade and agriculture.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e290efc8190b22c95dcd3e5f57f |
completed | April 16, 2026, 1:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff0b43bfcc8190b1b373ee10786f1e |
completed | May 9, 2026, 10:24 a.m. |
Created at: April 10, 2026, 3:17 a.m.