Triple
T14098144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sokolovskaya |
E339308
|
entity |
| Predicate | genderFormOf |
P17779
|
FINISHED |
| Object | Sokolovsky |
E643755
|
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: Sokolovsky | Statement: [Sokolovskaya, genderFormOf, Sokolovsky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sokolovsky Context triple: [Sokolovskaya, genderFormOf, Sokolovsky]
-
A.
Sokolovsky
chosen
Sokolovsky is a Russian surname most notably associated with Soviet military commander Vasily Sokolovsky.
-
B.
Shchusev
Shchusev is a Russian surname most notably associated with Alexey Shchusev, a prominent Soviet architect known for designing Lenin's Mausoleum in Moscow.
-
C.
Sekulovich
Sekulovich is the original Serbian family surname of American actor Karl Malden, reflecting his ethnic heritage.
-
D.
Semyonov
Semyonov is a common Russian surname borne by numerous notable figures in fields such as literature, science, and military history.
-
E.
Firsov
Firsov is a Russian surname most notably associated with Anatoli Firsov, a legendary Soviet ice hockey forward.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de5fb926288190a7f0f50d1d585d76 |
completed | April 14, 2026, 3:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdf02638881908eff75453b6a2aab |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 10:22 p.m.