Triple
T6737459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aleksandr Matrosov |
E153991
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Matrosov |
E153991
|
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: Matrosov | Statement: [Aleksandr Matrosov, familyName, Matrosov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Matrosov Context triple: [Aleksandr Matrosov, familyName, Matrosov]
-
A.
Shaposhnikov
Shaposhnikov is a Russian surname most notably associated with Soviet military leader Boris Shaposhnikov.
-
B.
Mikhaylovich
Mikhaylovich is a Russian patronymic name indicating that a person is the son of someone named Mikhail.
-
C.
Ratmir
Ratmir is a Tatar prince who appears as a gallant yet ultimately reformed seducer in Alexander Pushkin’s narrative poem "Ruslan and Ludmila."
-
D.
Akhromeyev
Akhromeyev is the surname of Sergei Akhromeyev, a prominent Soviet military leader and Marshal of the Soviet Union.
-
E.
Aleksandr Matrosov
chosen
Aleksandr Matrosov was a Soviet Red Army soldier famed for sacrificing his life by blocking an enemy machine-gun with his body during World War II, becoming a symbol of wartime heroism in the USSR.
- 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_69c6880d84d8819095d19de2295f26ac |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1850a288190aa7e647fefbb0ede |
completed | March 27, 2026, 6:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c70b0b97248190bf6bac160fe3d45b |
completed | March 27, 2026, 10:56 p.m. |
Created at: March 27, 2026, 2:10 p.m.