Triple
T14345864
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludvík |
E355717
|
entity |
| Predicate | variantSpelling |
P457
|
FINISHED |
| Object | Ludvik |
E355717
|
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: Ludvik | Statement: [Ludvík, variantSpelling, Ludvik]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ludvik Context triple: [Ludvík, variantSpelling, Ludvik]
-
A.
Ludvík
chosen
Ludvík is a masculine given name of Slavic origin, commonly used in Czech and Slovak cultures.
-
B.
Gustáv
Gustáv is a masculine given name of Slavic origin, commonly used in Central and Eastern Europe.
-
C.
Ottokar
Ottokar is a Germanic given name, historically borne by several Central European nobles and rulers, particularly in Austria and Bohemia.
-
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.
Vratislav
Vratislav is a historical Slavic personal name, borne by several medieval rulers and nobles in Central Europe, particularly in the Czech lands.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e8b81bc8190ace2a575faf55cc0 |
completed | April 14, 2026, 6:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe967e9c208190a00a82122b8c884c |
completed | May 9, 2026, 2:05 a.m. |
Created at: April 10, 2026, 1:14 a.m.