Triple
T8411240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petro Doroshenko |
E198628
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object |
Doroshenko
Doroshenko is a Ukrainian surname most notably borne by Petro Doroshenko, a 17th-century Cossack Hetman of Right-bank Ukraine.
|
E734798
|
NE FINISHED |
How this triple was built (4 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: Doroshenko | Statement: [Petro Doroshenko, familyName, Doroshenko]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Doroshenko Context triple: [Petro Doroshenko, familyName, Doroshenko]
-
A.
Mykola
Mykola is the Ukrainian form of the given name Nicholas, commonly used in Ukraine and among Ukrainian communities.
-
B.
Razumkov
Razumkov is a Ukrainian surname most prominently associated with Dmytro Razumkov, a contemporary Ukrainian politician and former Chairman of the Verkhovna Rada.
-
C.
Dmytrii
Dmytrii is a masculine given name of Slavic origin, related to the Greek name Demetrius and commonly used in Eastern European cultures.
-
D.
Oleksiy
Oleksiy is a common Ukrainian male given name, equivalent to Alexei or Alexey in Russian and Alexius in Latin.
-
E.
Vadym
Vadym is a masculine given name of Slavic origin, commonly used in Ukraine and other Eastern European countries.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Doroshenko Triple: [Petro Doroshenko, familyName, Doroshenko]
Generated description
Doroshenko is a Ukrainian surname most notably borne by Petro Doroshenko, a 17th-century Cossack Hetman of Right-bank Ukraine.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Doroshenko Target entity description: Doroshenko is a Ukrainian surname most notably borne by Petro Doroshenko, a 17th-century Cossack Hetman of Right-bank Ukraine.
-
A.
Mykola
Mykola is the Ukrainian form of the given name Nicholas, commonly used in Ukraine and among Ukrainian communities.
-
B.
Razumkov
Razumkov is a Ukrainian surname most prominently associated with Dmytro Razumkov, a contemporary Ukrainian politician and former Chairman of the Verkhovna Rada.
-
C.
Dmytrii
Dmytrii is a masculine given name of Slavic origin, related to the Greek name Demetrius and commonly used in Eastern European cultures.
-
D.
Oleksiy
Oleksiy is a common Ukrainian male given name, equivalent to Alexei or Alexey in Russian and Alexius in Latin.
-
E.
Vadym
Vadym is a masculine given name of Slavic origin, commonly used in Ukraine and other Eastern European countries.
- F. None of above. chosen
Provenance (5 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83dec1f08190ae08719e860b29fa |
completed | March 31, 2026, 8:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce1d3d9f848190bd425b80aa58a376 |
completed | April 2, 2026, 7:39 a.m. |
| NEDg | Description generation | batch_69ce2133972881909c7a4b44d6799d9e |
completed | April 2, 2026, 7:56 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69ce21e74d9481908f04b2ab5b57f8a5 |
completed | April 2, 2026, 7:59 a.m. |
Created at: March 30, 2026, 6:05 p.m.