Triple
T20936413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zdzisław Jeziorański |
E515596
|
entity |
| Predicate | hasGivenName |
P17
|
FINISHED |
| Object | Zdzisław |
—
|
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: Zdzisław | Statement: [Zdzisław Jeziorański, hasGivenName, Zdzisław]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zdzisław Context triple: [Zdzisław Jeziorański, hasGivenName, Zdzisław]
-
A.
Zdzisław
chosen
Zdzisław is a Polish masculine given name of Slavic origin, traditionally borne by nobles, politicians, and cultural figures.
-
B.
Czesław
Czesław is a Polish masculine given name, historically borne by notable figures such as Nobel Prize–winning poet Czesław Miłosz.
-
C.
Jerzy
Jerzy is a masculine given name of Slavic origin, particularly common in Poland as the equivalent of George.
-
D.
Walery Sławek
Walery Sławek was a Polish politician, close associate of Józef Piłsudski, who served multiple times as Prime Minister of Poland during the interwar period.
-
E.
Tadeusz Zaleski
Tadeusz Zaleski is a Polish individual notable enough to be recognized as a prominent bearer of the surname Zaleski.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f9527004819082b72bf15e3c6419 |
completed | April 21, 2026, 4:13 a.m. |
Created at: April 16, 2026, 12:49 p.m.