Triple
T21691307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lev Sedov |
E535375
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Sedov |
—
|
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: Sedov | Statement: [Lev Sedov, familyName, Sedov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sedov Context triple: [Lev Sedov, familyName, Sedov]
-
A.
Sedov
chosen
Sedov is a Russian surname most notably associated with Lev Sedov, the revolutionary son of Leon Trotsky.
-
B.
Bykovsky
Bykovsky is a rural locality (selo) in the Bulunsky District of the Sakha Republic, Russia, situated in the Arctic region along the Lena River.
-
C.
Belanov
Belanov is a Ukrainian surname most famously associated with Igor Belanov, the former Soviet footballer and Ballon d'Or winner.
-
D.
Kozhedub
Kozhedub is a Slavic surname most famously borne by Ivan Kozhedub, a highly decorated Soviet World War II fighter ace.
-
E.
Saha
Saha is a surname most notably associated with Indian astrophysicist Meghnad Saha, known for the Saha ionization equation in stellar astrophysics.
- 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_69e0c46a6ee481908836e1420fb78c9b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef96cfaab08190b400e1538afc8c43 |
completed | April 27, 2026, 5:03 p.m. |
Created at: April 16, 2026, 6:45 p.m.