Triple
T18232211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karol Lipiński |
E436569
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Lipiński |
—
|
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: Lipiński | Statement: [Karol Lipiński, familyName, Lipiński]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lipiński Context triple: [Karol Lipiński, familyName, Lipiński]
-
A.
Lipiński
chosen
Lipiński is a Polish surname borne by various notable figures in fields such as music, sports, and science.
-
B.
Wdowiński
Wdowiński is a Polish surname most notably borne by Dawid Wdowiński, a Jewish-Polish neurologist and Zionist activist involved in the Warsaw Ghetto resistance.
-
C.
Kiliński
Kiliński is a Polish surname most notably borne by Jan Kiliński, a celebrated shoemaker and insurgent leader in the Kościuszko Uprising.
-
D.
Lipski
Lipski is a Polish surname borne by various notable figures in politics, arts, and academia.
-
E.
Pietraszewicz
Pietraszewicz is a Polish surname associated with individuals such as Bronisław "Lot" Pietraszewicz.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b414308190bc7dd8e73c0a362c |
completed | April 19, 2026, 3:28 p.m. |
Created at: April 10, 2026, 10:33 a.m.