Triple
T19425952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaminsky |
E485979
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Kaminskiy |
—
|
NE NERFINISHED |
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: Kaminskiy | Statement: [Kaminsky, hasVariant, Kaminskiy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kaminskiy Context triple: [Kaminsky, hasVariant, Kaminskiy]
-
A.
Klimowitschi
Klimowitschi is a town in Belarus known in part for its international municipal partnership with Werder (Havel) in Germany.
-
B.
Kamiński
Kamiński is a common Polish surname borne by numerous notable figures in fields such as film, sports, and politics.
-
C.
Каминский
chosen
Каминский is a Slavic surname, common in Russian- and Polish-speaking regions, borne by various notable figures in fields such as politics, sports, and the arts.
-
D.
Karski
Karski is a Polish surname most famously borne by Jan Karski, the World War II resistance courier who reported on the Holocaust to the Allies.
-
E.
Czeremcha
Czeremcha is a village in northeastern Poland that serves as a local railway junction and border-area transport hub near Belarus.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8d688f881909c85104a62e09d8a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63218772c8190a48b6cb01bd12b73 |
completed | April 20, 2026, 2:03 p.m. |
Created at: April 10, 2026, 1:37 p.m.