Triple
T12809135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ukraine–Poland |
E306221
|
entity |
| Predicate | hasEthnicGroup |
P1898
|
FINISHED |
| Object | Boykos |
E193150
|
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: Boykos | Statement: [Ukraine–Poland, hasEthnicGroup, Boykos]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Boykos Context triple: [Ukraine–Poland, hasEthnicGroup, Boykos]
-
A.
Boykos
chosen
Boykos are a distinct East Slavic highlander ethnic group traditionally inhabiting the Carpathian Mountains region of western Ukraine and neighboring areas.
-
B.
Kovpak
Kovpak is a Ukrainian surname most notably associated with Sydir Kovpak, a famed Soviet partisan leader during World War II.
-
C.
Kostenko
Kostenko is a Slavic surname of Ukrainian and Russian origin borne by various notable figures in politics, military, arts, and sports.
-
D.
Baklanov
Baklanov is a Russian surname most notably associated with Soviet politician and aerospace official Oleg Baklanov.
-
E.
Koshovyi
Koshovyi is a Ukrainian surname most notably associated with comedian and actor Yevhen Koshovyi.
- 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_69d7bdf46c448190b1faa55aaacb6317 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e808130819080f404b3a7462c2e |
completed | April 10, 2026, 9:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f68ec89eb081909915af6e2216e0a2 |
completed | May 2, 2026, 11:54 p.m. |
Created at: April 9, 2026, 5:31 p.m.