Triple
T19648841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bohuslav Sobotka |
E471753
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Bohuslav |
—
|
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: Bohuslav | Statement: [Bohuslav Sobotka, givenName, Bohuslav]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bohuslav Context triple: [Bohuslav Sobotka, givenName, Bohuslav]
-
A.
Bohuslav
chosen
Bohuslav is a Czech masculine given name of Slavic origin, historically borne by several notable figures including composers and politicians.
-
B.
Bohuslav
Bohuslav is a settlement located within Bila Tserkva Raion in Kyiv Oblast, Ukraine.
-
C.
Jan Blahoslav
Jan Blahoslav was a 16th-century Czech humanist, bishop of the Unity of the Brethren, and scholar best known for his contributions to Czech Bible translation and language.
-
D.
Oldřich
Oldřich is a Czech masculine given name traditionally borne by several notable historical and cultural figures in the Czech lands.
-
E.
Ladislav
Ladislav is a masculine given name of Slavic origin, commonly used in Central and Eastern Europe.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e641278e9881909bdf8d440ef6eba4 |
completed | April 20, 2026, 3:07 p.m. |
Created at: April 10, 2026, 1:44 p.m.