Triple
T16403067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rada Adzhubei |
E398346
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Alexei Adzhubei |
E1239169
|
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: Alexei Adzhubei | Statement: [Rada Adzhubei, spouse, Alexei Adzhubei]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Alexei Adzhubei Context triple: [Rada Adzhubei, spouse, Alexei Adzhubei]
-
A.
Alexei Adzhubei
chosen
Alexei Adzhubei was a Soviet journalist and editor-in-chief of the newspaper Izvestia, best known as the son-in-law of Soviet leader Nikita Khrushchev.
-
B.
Alexander Skovorodin
Alexander Skovorodin was a Russian figure significant enough—likely a local statesman, military officer, or notable public figure—to have the town of Skovorodino named in his honor.
-
C.
Yakov Belopolsky
Yakov Belopolsky was a Soviet architect known for designing major war memorials and monumental public works in the USSR.
-
D.
Ilya Segalovich
Ilya Segalovich was a Russian computer scientist and entrepreneur best known as the co-founder and chief technology officer of the Yandex search engine.
-
E.
Yury Vdovin
Yury Vdovin is an architect known for his work on the design of the VDNKh exhibition complex in Moscow.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e327d12dc08190a5b497692b667ed7 |
completed | April 18, 2026, 6:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d447f5cc81908757869f2d1e94a1 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:09 a.m.