Triple
T21141399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nikolai Goncharov |
E520936
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Goncharov |
—
|
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: Goncharov | Statement: [Nikolai Goncharov, familyName, Goncharov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Goncharov Context triple: [Nikolai Goncharov, familyName, Goncharov]
-
A.
Nikolai Goncharov
chosen
Nikolai Goncharov is a lesser-known relative of the Russian avant-garde artist Natalia Goncharova, noted primarily in biographical references to her family.
-
B.
Tolstaya
Tolstaya is a Russian noble family name most famously borne by Sophia Tolstaya, the wife and muse of writer Leo Tolstoy.
-
C.
Possokhov
Possokhov is the surname of Yuri Possokhov, a prominent Russian ballet dancer and choreographer.
-
D.
Ivan Yefimovich Petrov
Ivan Yefimovich Petrov was a Soviet military commander and general noted for his leadership of Red Army forces on the Eastern Front during World War II.
-
E.
Rozhdestvensky
Rozhdestvensky is a Russian surname most notably associated with figures such as conductor Gennady Rozhdestvensky.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e723f96cf081909d10309e08aeca93 |
completed | April 21, 2026, 7:15 a.m. |
Created at: April 16, 2026, 2:57 p.m.