Triple
T20231435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piekarski |
E495534
|
entity |
| Predicate | hasNotableBearer |
P458
|
FINISHED |
| Object |
Rafał Piekarski
Rafał Piekarski is a person notable enough to be recognized as a distinguished bearer of the surname Piekarski.
|
E1447902
|
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: Rafał Piekarski | Statement: [Piekarski, hasNotableBearer, Rafał Piekarski]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Rafał Piekarski Context triple: [Piekarski, hasNotableBearer, Rafał Piekarski]
-
A.
Mariusz Piekarski
Mariusz Piekarski is a Polish former professional footballer known for playing as a midfielder for clubs in Poland and abroad.
-
B.
Cezary Piekarski
Cezary Piekarski is a Polish individual known primarily as a notable bearer of the surname Piekarski.
-
C.
Krzysztof Piekarski
Krzysztof Piekarski is a person notable enough to be recognized as a prominent bearer of the surname Piekarski, though specific widely known public achievements are not clearly documented.
-
D.
Andrzej Piekarski
Andrzej Piekarski is a Polish individual notable enough to be recognized as a bearer of the surname Piekarski.
-
E.
Piotr Piekarski
Piotr Piekarski is a Polish middle-distance runner who specialized in the 800 metres and competed internationally in the late 20th century.
- 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: Rafał Piekarski Triple: [Piekarski, hasNotableBearer, Rafał Piekarski]
Generated description
Rafał Piekarski is a person notable enough to be recognized as a distinguished bearer of the surname Piekarski.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Rafał Piekarski Target entity description: Rafał Piekarski is a person notable enough to be recognized as a distinguished bearer of the surname Piekarski.
-
A.
Mariusz Piekarski
Mariusz Piekarski is a Polish former professional footballer known for playing as a midfielder for clubs in Poland and abroad.
-
B.
Cezary Piekarski
Cezary Piekarski is a Polish individual known primarily as a notable bearer of the surname Piekarski.
-
C.
Krzysztof Piekarski
Krzysztof Piekarski is a person notable enough to be recognized as a prominent bearer of the surname Piekarski, though specific widely known public achievements are not clearly documented.
-
D.
Andrzej Piekarski
Andrzej Piekarski is a Polish individual notable enough to be recognized as a bearer of the surname Piekarski.
-
E.
Piotr Piekarski
Piotr Piekarski is a Polish middle-distance runner who specialized in the 800 metres and competed internationally in the late 20th century.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fddafac819089cef4158f5e0ab5 |
completed | April 20, 2026, 6:26 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08e8202e748190a043ac51dc8faa01 |
completed | May 16, 2026, 9:56 p.m. |
| NEDg | Description generation | batch_6a08e88b1e1c8190a02a52e50470ce79 |
completed | May 16, 2026, 9:58 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a08e923a134819082e8d677c420f8ce |
completed | May 16, 2026, 10:01 p.m. |
Created at: April 11, 2026, 11:39 p.m.