Triple
T7041298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kowalski |
E163517
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Kowalskiy |
E163517
|
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: Kowalskiy | Statement: [Kowalski, hasVariant, Kowalskiy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kowalskiy Context triple: [Kowalski, hasVariant, Kowalskiy]
-
A.
Kowalski
chosen
Kowalski is a surname of Polish origin commonly used in Poland and among Polish diaspora communities.
-
B.
Kowal
Kowal is a small town in central Poland historically notable as the birthplace of King Casimir III the Great.
-
C.
Kowarski
Kowarski is a surname most notably associated with Lew Kowarski, a pioneering physicist in the development of nuclear reactors and early nuclear research in Europe.
-
D.
Kornienko
Kornienko is a Ukrainian surname most notably borne by Oleksandr Kornienko, a contemporary Ukrainian politician and public figure.
-
E.
Lopatynski
Lopatynski is the original Polish family name of Eddie Lopat, a notable Major League Baseball pitcher and later coach.
- 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_69c6885e7c1c8190be32a8f79ab4e0cf |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e22544708190b0dffb5256d4cda6 |
completed | March 27, 2026, 8:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7886a24c48190bb461f26f87d6ef8 |
completed | March 28, 2026, 7:51 a.m. |
Created at: March 27, 2026, 2:36 p.m.