Triple
T16816688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakub Jasiński |
E408769
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object |
Jasiński
Jasiński is a Polish surname commonly borne by individuals of Polish origin, including notable historical and contemporary figures.
|
E1236105
|
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: Jasiński | Statement: [Jakub Jasiński, familyName, Jasiński]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jasiński Context triple: [Jakub Jasiński, familyName, Jasiński]
-
A.
Rodziński
Rodziński is a Polish surname most notably associated with Artur Rodziński, a prominent 20th-century orchestral conductor.
-
B.
Żymierski
Żymierski is a Polish surname most notably associated with Michał Rola-Żymierski, a high-ranking military commander and communist-era Marshal of Poland.
-
C.
Ogiński
Ogiński is the surname of a prominent Polish–Lithuanian noble family best known for composer and statesman Michał Kleofas Ogiński.
-
D.
Niedziałkowski
Niedziałkowski is a Polish surname most notably borne by Mieczysław Niedziałkowski, a prominent interwar socialist politician and publicist.
-
E.
Żółkiewski
Żółkiewski is a Polish noble surname most famously associated with the hetman and statesman Stanisław Żółkiewski of the Polish–Lithuanian Commonwealth.
- 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: Jasiński Triple: [Jakub Jasiński, familyName, Jasiński]
Generated description
Jasiński is a Polish surname commonly borne by individuals of Polish origin, including notable historical and contemporary figures.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Jasiński Target entity description: Jasiński is a Polish surname commonly borne by individuals of Polish origin, including notable historical and contemporary figures.
-
A.
Rodziński
Rodziński is a Polish surname most notably associated with Artur Rodziński, a prominent 20th-century orchestral conductor.
-
B.
Żymierski
Żymierski is a Polish surname most notably associated with Michał Rola-Żymierski, a high-ranking military commander and communist-era Marshal of Poland.
-
C.
Ogiński
Ogiński is the surname of a prominent Polish–Lithuanian noble family best known for composer and statesman Michał Kleofas Ogiński.
-
D.
Niedziałkowski
Niedziałkowski is a Polish surname most notably borne by Mieczysław Niedziałkowski, a prominent interwar socialist politician and publicist.
-
E.
Żółkiewski
Żółkiewski is a Polish noble surname most famously associated with the hetman and statesman Stanisław Żółkiewski of the Polish–Lithuanian Commonwealth.
- 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_69d88394566c8190b3dcbdc72935f7fa |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b2e1de908190aa3508770fb865cf |
completed | April 18, 2026, 4:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb0f863081908e74dc4a7c91e91d |
completed | May 10, 2026, 5:06 p.m. |
| NEDg | Description generation | batch_6a00bb9b2b1881908f9f5c3dd1a2d500 |
completed | May 10, 2026, 5:08 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a00bc3a4b888190bd190b9330e2777d |
completed | May 10, 2026, 5:11 p.m. |
Created at: April 10, 2026, 5:23 a.m.