Triple
T16595951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamil Grosicki |
E403206
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object |
Grosicki
Grosicki is a Polish surname most notably borne by professional footballer Kamil Grosicki, a winger known for his pace and international appearances for Poland.
|
E1222853
|
NE FINISHED |
How this triple was built (4 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: Grosicki | Statement: [Kamil Grosicki, familyName, Grosicki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Grosicki Context triple: [Kamil Grosicki, familyName, Grosicki]
-
A.
Grodzinski
Grodzinski is a Jewish surname most prominently associated with the influential Lithuanian rabbi and halachic authority Chaim Ozer Grodzinski.
-
B.
Bielecki
Bielecki is a Polish surname borne by various notable individuals across fields such as politics, sports, and mountaineering.
-
C.
Gęsicki
Gęsicki is a Polish surname borne by individuals such as Zbigniew Gęsicki, a resistance fighter known by the pseudonym "Juno."
-
D.
Grósz
Grósz is a Hungarian surname most notably borne by Károly Grósz, a late-20th-century Hungarian communist politician and former Prime Minister.
-
E.
Krupiński
Krupiński is a Polish surname, often borne by individuals of Polish origin and sometimes spelled in variant forms such as Kropinski.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Grosicki Triple: [Kamil Grosicki, familyName, Grosicki]
Generated description
Grosicki is a Polish surname most notably borne by professional footballer Kamil Grosicki, a winger known for his pace and international appearances for Poland.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Grosicki Target entity description: Grosicki is a Polish surname most notably borne by professional footballer Kamil Grosicki, a winger known for his pace and international appearances for Poland.
-
A.
Grodzinski
Grodzinski is a Jewish surname most prominently associated with the influential Lithuanian rabbi and halachic authority Chaim Ozer Grodzinski.
-
B.
Bielecki
Bielecki is a Polish surname borne by various notable individuals across fields such as politics, sports, and mountaineering.
-
C.
Gęsicki
Gęsicki is a Polish surname borne by individuals such as Zbigniew Gęsicki, a resistance fighter known by the pseudonym "Juno."
-
D.
Grósz
Grósz is a Hungarian surname most notably borne by Károly Grósz, a late-20th-century Hungarian communist politician and former Prime Minister.
-
E.
Krupiński
Krupiński is a Polish surname, often borne by individuals of Polish origin and sometimes spelled in variant forms such as Kropinski.
- F. None of above. chosen
Provenance (5 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e35d717604819083ed60b865bbd13e |
completed | April 18, 2026, 10:31 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00759fe6ec81908c5321dcba558269 |
completed | May 10, 2026, 12:10 p.m. |
| NEDg | Description generation | batch_6a007825547c81909230ac39761fba96 |
completed | May 10, 2026, 12:20 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a00788e103481908d40bbe4a3cb1695 |
completed | May 10, 2026, 12:22 p.m. |
Created at: April 10, 2026, 5:16 a.m.