Triple
T5379937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oleksiy Honcharuk |
E113055
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Honcharuk |
E113055
|
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: Honcharuk | Statement: [Oleksiy Honcharuk, familyName, Honcharuk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Honcharuk Context triple: [Oleksiy Honcharuk, familyName, Honcharuk]
-
A.
Honcharuk
chosen
Honcharuk is a Ukrainian surname most notably associated with Oleksiy Honcharuk, a former Prime Minister of Ukraine.
-
B.
Hankutchin
Hankutchin is an alternative name for the Hän, an Athabaskan-speaking Indigenous people of the Yukon–Alaska border region.
-
C.
Chaek
Chaek is a Korean given name most notably borne by Kim Chaek, a prominent North Korean military and political figure.
-
D.
Chára
Chára is a Slovak surname most prominently associated with Zdeno Chára, the towering NHL defenseman and Stanley Cup champion.
-
E.
Harku
Harku is a small settlement in northern Estonia located within Harku Parish, near the capital city of Tallinn.
- 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_69bd4436a1988190af18dcff7fd306b4 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd86ce56c88190a66b3852416edccb |
completed | March 20, 2026, 5:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf2949cd9881908ca0d8fdf1642f71 |
completed | March 21, 2026, 11:27 p.m. |
Created at: March 20, 2026, 2:03 p.m.