Triple
T11037485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Irina Godunova |
E260922
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Godunova |
E908137
|
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: Godunova | Statement: [Irina Godunova, familyName, Godunova]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Godunova Context triple: [Irina Godunova, familyName, Godunova]
-
A.
Godunova
chosen
Godunova is the feminine form of the Russian surname Godunov, historically associated with the noble Godunov family of Russia.
-
B.
Brezhneva
Brezhneva is a Russian surname most notably borne by Viktoria Brezhneva, the wife of Soviet leader Leonid Brezhnev.
-
C.
Pugacheva
Pugacheva is a Russian surname most famously borne by iconic Soviet and Russian pop singer Alla Pugacheva.
-
D.
Galina
Galina is a feminine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
E.
Ulitsa Gorchakova
Ulitsa Gorchakova is a Moscow Metro station on the Butovskaya Line serving the Yuzhnoye Butovo District in southern 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797fd5fe081908af13835b18de7b8 |
completed | April 9, 2026, 12:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e4831ba3688190bee08ca29872ab3b |
completed | April 19, 2026, 7:24 a.m. |
Created at: April 8, 2026, 9:25 p.m.