Triple
T10026636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genndy Tartakovsky |
E200745
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Gennady |
E279793
|
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: Gennady | Statement: [Genndy Tartakovsky, givenName, Gennady]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gennady Context triple: [Genndy Tartakovsky, givenName, Gennady]
-
A.
Gennady
chosen
Gennady is a masculine given name of Slavic origin, commonly used in Russia and other Eastern European countries.
-
B.
Gennadi
Gennadi is a coastal village on the southern part of the Greek island of Rhodes, known for its long beach and traditional architecture.
-
C.
Anatoly
Anatoly is a masculine given name of Slavic origin, commonly used in Russian-speaking countries.
-
D.
Leonid
Leonid is a masculine given name of Slavic origin, notably borne by Soviet leader Leonid Brezhnev.
-
E.
Georgy Vinogradov
Georgy Vinogradov was a Soviet-era Russian singer known for his lyrical tenor voice and popular performances of wartime and patriotic songs.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcde3c1b88190924e6158f406b453 |
completed | April 2, 2026, 2:01 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d26ac2f14081908deaf3945491af78 |
completed | April 5, 2026, 1:59 p.m. |
Created at: March 30, 2026, 8:54 p.m.