Triple
T8689745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zbigniew |
E206255
|
entity |
| Predicate | hasVariantForm |
P457
|
FINISHED |
| Object | Zbygniew |
E206255
|
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: Zbygniew | Statement: [Zbigniew, hasVariantForm, Zbygniew]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zbygniew Context triple: [Zbigniew, hasVariantForm, Zbygniew]
-
A.
Zbigniew
chosen
Zbigniew is a masculine Slavic given name, particularly common in Poland.
-
B.
Bronisław
Bronisław is a masculine Slavic given name, particularly common in Poland, borne by several notable historical and cultural figures.
-
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.
Zawisza
Zawisza is a Polish surname historically associated with several notable figures, including nobles, politicians, and cultural personalities.
-
E.
Jędrzej
Jędrzej is a Polish male given name, traditionally used as a regional or archaic form of the name Andrzej (Andrew).
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5734602c81909a0687e00f4a4a26 |
completed | March 31, 2026, 11:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf427fb1988190ab9fd810423ced84 |
completed | April 3, 2026, 4:30 a.m. |
Created at: March 30, 2026, 6:33 p.m.