Triple
T22174824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Štěpán |
E548019
|
entity |
| Predicate | hasDiminutive |
P456
|
FINISHED |
| Object | Štěpík |
—
|
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: Štěpík | Statement: [Štěpán, hasDiminutive, Štěpík]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Štěpík Context triple: [Štěpán, hasDiminutive, Štěpík]
-
A.
Štěpán
chosen
Štěpán is the Czech given name corresponding to the Hungarian name István, itself equivalent to Stephen in English.
-
B.
Jelínek
Jelínek is a Czech surname commonly borne by individuals of Czech origin and appears in various cultural, academic, and professional contexts.
-
C.
Gabčík
Gabčík is a Slovak surname most notably borne by Jozef Gabčík, a World War II resistance fighter involved in the assassination of Nazi official Reinhard Heydrich.
-
D.
Zbyněk
Zbyněk is a masculine given name of Czech origin commonly used in the Czech Republic and among Czech-speaking communities.
-
E.
Krejčíř
Krejčíř is a Czech surname most notably associated with Radovan Krejčíř, a convicted criminal and fugitive involved in high-profile fraud and organized crime cases.
- 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_69e11e3d53f88190a2b690e3f25bb062 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12a6b755c81909e9bd2a588c065b3 |
completed | April 28, 2026, 9:45 p.m. |
Created at: April 16, 2026, 8:34 p.m.