Triple
T16005950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikuláš Dzurinda |
E388218
|
entity |
| Predicate | givenName |
P17
|
FINISHED |
| Object | Mikuláš |
E632536
|
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: Mikuláš | Statement: [Mikuláš Dzurinda, givenName, Mikuláš]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mikuláš Context triple: [Mikuláš Dzurinda, givenName, Mikuláš]
-
A.
Mikuláš
chosen
Mikuláš is the Czech name for Saint Nicholas, a traditional Christian figure associated with gift-giving and the inspiration for modern Santa Claus customs in Central Europe.
-
B.
Mikołaj
Mikołaj is a Polish masculine given name, equivalent to Nicholas, commonly used in Poland and other Slavic countries.
-
C.
Mikuláš of Kadaň
Mikuláš of Kadaň was a medieval Czech clockmaker and craftsman renowned for his role in creating Prague’s famous astronomical clock.
-
D.
St. Niklaus
St. Niklaus is a locality within the Swiss municipality of Feldbrunnen-St. Niklaus in the canton of Solothurn.
-
E.
Milak
Milak is a border town in India’s Uttar Pradesh state, known as a road-linked crossing point on the route to Afghanistan via Zaranj.
- 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_69d86dabcb7c8190b6a39d6831d2fa1b |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e157ff33d88190b5a92f7ff70b24eb |
completed | April 16, 2026, 9:43 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffc3dec0c0819099b9007ad0fc6fb4 |
completed | May 9, 2026, 11:31 p.m. |
Created at: April 10, 2026, 4:55 a.m.