Triple
T16497313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronisław Kaper |
E400717
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Bronisław |
E558406
|
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: Bronisław | Statement: [Bronisław Kaper, givenName, Bronisław]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bronisław Context triple: [Bronisław Kaper, givenName, Bronisław]
-
A.
Bronisław
chosen
Bronisław is a masculine Slavic given name, particularly common in Poland, borne by several notable historical and cultural figures.
-
B.
Mieczysław
Mieczysław is a traditional Slavic male given name, particularly common in Poland, derived from elements meaning "sword" and "glory" or "fame."
-
C.
Zbigniew
Zbigniew is a masculine Slavic given name, particularly common in Poland.
-
D.
Bogusław
Bogusław was the original Slavic birth name of Eric of Pomerania, the medieval king who ruled over the Kalmar Union of Denmark, Norway, and Sweden.
-
E.
Walery
Walery is a masculine given name of Slavic origin, used primarily in Polish-speaking countries.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e343a7c81909e04cbaaa40e2531 |
completed | April 18, 2026, 7:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00607cbc80819088505d8bdd663109 |
completed | May 10, 2026, 10:39 a.m. |
Created at: April 10, 2026, 5:14 a.m.