Triple
T18010310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgy Sedov |
E430859
|
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: [Georgy Sedov, familyName, Sedov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sedov Context triple: [Georgy 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.
Kozhedub
Kozhedub is a Slavic surname most famously borne by Ivan Kozhedub, a highly decorated Soviet World War II fighter ace.
-
D.
Saha
Saha is a surname most notably associated with Indian astrophysicist Meghnad Saha, known for the Saha ionization equation in stellar astrophysics.
-
E.
Saha
Saha is a small town in the Ambala district of the northern Indian state of Haryana, known primarily as a local commercial and transport hub for surrounding rural areas.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b51f0a488190bd34e1f9039f4dc9 |
completed | April 19, 2026, 10:57 a.m. |
Created at: April 10, 2026, 10:24 a.m.