Triple
T16240117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gennady Burbulis |
E394220
|
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: [Gennady Burbulis, givenName, Gennady]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gennady Context triple: [Gennady Burbulis, 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.
Gennady Tsygurov
Gennady Tsygurov was a Soviet and Russian ice hockey defenceman and coach, known for his long career in domestic leagues and contributions to player development.
- 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_69d87f2171208190951025e526947816 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2455d5270819090171d4207223a28 |
completed | April 17, 2026, 2:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a000edd1ed08190aa0211c3b17a918e |
completed | May 10, 2026, 4:51 a.m. |
Created at: April 10, 2026, 5:04 a.m.