Triple
T7135348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bronisław Geremek |
E166293
|
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 Geremek, givenName, Bronisław]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bronisław Context triple: [Bronisław Geremek, 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.
Zbigniew
Zbigniew is a masculine Slavic given name, particularly common in Poland.
-
C.
Stanislaw
Stanislaw is a masculine given name of Slavic origin, most notably borne by the Polish-American mathematician Stanislaw Ulam.
-
D.
Bronisław Duch
Bronisław Duch was a Polish general best known for leading Polish forces in exile during World War II, including distinguished service in the Italian Campaign.
-
E.
Tadeusz
Tadeusz is a masculine given name of Slavic origin, particularly common in Poland.
- 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_69c68884a9388190af42f90d1c1a7151 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e690f954819084b81a555f4cdb5e |
completed | March 27, 2026, 8:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7cbd551288190a53decc7021929ee |
completed | March 28, 2026, 12:38 p.m. |
Created at: March 27, 2026, 2:45 p.m.