Triple
T14457234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leszek |
E358487
|
entity |
| Predicate | relatedName |
P3889
|
FINISHED |
| Object | Leszko |
E358487
|
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: Leszko | Statement: [Leszek, relatedName, Leszko]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leszko Context triple: [Leszek, relatedName, Leszko]
-
A.
Leszek
chosen
Leszek is a masculine Slavic given name historically borne by several Polish rulers and nobles.
-
B.
Lucjan
Lucjan is a masculine given name of Latin origin, commonly used in Poland and other Slavic countries.
-
C.
Zbyszek
Zbyszek is a common Polish diminutive form of the male given name Zbigniew.
-
D.
Wasilewski
Wasilewski is a Polish surname, typically indicating familial or geographic origin and commonly found in Poland and among the Polish diaspora.
-
E.
Alojzy
Alojzy is a Polish given name, most commonly recognized as the Polish form of the name Aloysius.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91a9c0d48190ae015e5e0db806ca |
completed | April 14, 2026, 7:12 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd64935d8081908e5b0e80027948e0 |
completed | May 8, 2026, 4:20 a.m. |
Created at: April 10, 2026, 1:19 a.m.