Triple
T14486189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alois Jirásek |
E359233
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Jirásek |
E359233
|
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: Jirásek | Statement: [Alois Jirásek, familyName, Jirásek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jirásek Context triple: [Alois Jirásek, familyName, Jirásek]
-
A.
Jiří
Jiří is a common Czech male given name, equivalent to George in English.
-
B.
Havlíček
Havlíček is a Czech surname most famously associated with basketball Hall of Famer John Havlicek and several notable Czech cultural and public figures.
-
C.
Jáchym
Jáchym is a masculine given name of Slavic origin, commonly used in Czech and Slovak cultures and related to the name Joachim.
-
D.
Zdeněk
Zdeněk is a Czech given name commonly used for males, equivalent to the English name Sidney or Dennis in some contexts.
-
E.
Alois Jirásek
chosen
Alois Jirásek was a prominent Czech writer and playwright best known for his historical novels that helped shape modern Czech national identity.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de924ee0f08190baf68318b41fa64d |
completed | April 14, 2026, 7:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd8aaaf74481909aeda3627bea39a9 |
completed | May 8, 2026, 7:03 a.m. |
Created at: April 10, 2026, 1:20 a.m.