Triple
T3050652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Miroslav Šatan |
E83560
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Miroslav |
E95945
|
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: Miroslav | Statement: [Miroslav Šatan, givenName, Miroslav]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Miroslav Context triple: [Miroslav Šatan, givenName, Miroslav]
-
A.
Miroslav
chosen
Miroslav is a common Slavic male given name, notably borne by Slovak ice hockey star Miroslav Šatan.
-
B.
Timotej
Timotej is a masculine given name, common in Slavic countries, that is equivalent to Timothy.
-
C.
Miroslav Tyrš
Miroslav Tyrš was a Czech art historian, philosopher, and nationalist who co-founded the Sokol movement, which combined physical education with cultural and patriotic ideals in the Czech lands.
-
D.
Jozef
Jozef is a masculine given name of Hebrew origin, commonly used in Central and Eastern Europe as a variant of Joseph.
-
E.
Vojtech
Vojtech 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 (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_69ad8b24924c8190a9bb6f61d519e4ae |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9bb1a46081908547a2f27cbf3446 |
completed | March 8, 2026, 3:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b1eefa84f08190a178cc0674d8a3ab |
completed | March 11, 2026, 10:38 p.m. |
Created at: March 8, 2026, 3:01 p.m.