Triple
T17789809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zygmunt Janiszewski |
E444125
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Zygmunt |
—
|
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: Zygmunt | Statement: [Zygmunt Janiszewski, givenName, Zygmunt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zygmunt Context triple: [Zygmunt Janiszewski, givenName, Zygmunt]
-
A.
Zygmunt
chosen
Zygmunt is a masculine given name of Polish origin, historically borne by several notable figures in Poland.
-
B.
Władysław
Władysław is a Polish masculine given name historically borne by several notable figures, including kings and political leaders.
-
C.
Mieczysław
Mieczysław is a traditional Slavic male given name, particularly common in Poland, derived from elements meaning "sword" and "glory" or "fame."
-
D.
Zbigniew
Zbigniew is a masculine Slavic given name, particularly common in Poland.
-
E.
Bronisław
Bronisław is a masculine Slavic given name, particularly common in Poland, borne by several notable historical and cultural figures.
- 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_69d8b9ef17708190bdf7e2adbf14ddc2 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4879688908190a5428b1fa7525f62 |
completed | April 19, 2026, 7:43 a.m. |
Created at: April 10, 2026, 10:13 a.m.