Triple
T14076594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorky family |
E338750
|
entity |
| Predicate | hasFamilyName |
P18
|
FINISHED |
| Object | Peshkov |
E336064
|
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: Peshkov | Statement: [Gorky family, hasFamilyName, Peshkov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Peshkov Context triple: [Gorky family, hasFamilyName, Peshkov]
-
A.
Peshkov
chosen
Peshkov is a Russian surname most famously borne by Alexei Maximovich Peshkov, better known by his pen name Maxim Gorky, a prominent writer and political activist.
-
B.
Ignatyev
Ignatyev is a Russian surname borne by various notable figures in politics, military, sports, and the arts.
-
C.
Shchusev
Shchusev is a Russian surname most notably associated with Alexey Shchusev, a prominent Soviet architect known for designing Lenin's Mausoleum in Moscow.
-
D.
Tolbukhin
Tolbukhin is a Russian surname most notably associated with Soviet military commander Fyodor Tolbukhin, a prominent general during World War II.
-
E.
Solovyov
Solovyov is a Russian surname most notably associated with figures such as philosopher Vladimir Solovyov and various other prominent Russian cultural and public personalities.
- 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_69d81c687b0c819087fd9ed4198403f8 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5c5cdd288190914e1d57321b3554 |
completed | April 14, 2026, 3:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcd0a175a48190b596ea4cf917e80e |
completed | May 7, 2026, 5:49 p.m. |
Created at: April 9, 2026, 10:21 p.m.