Triple
T14129805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donovaly Pass |
E340130
|
entity |
| Predicate | SlovakName |
P25642
|
FINISHED |
| Object | Donovaly |
E300719
|
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: Donovaly | Statement: [Donovaly Pass, SlovakName, Donovaly]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Donovaly Context triple: [Donovaly Pass, SlovakName, Donovaly]
-
A.
Donovaly
chosen
Donovaly is a popular Slovak mountain village and ski resort known for its extensive slopes and winter sports facilities in the Low Tatras region.
-
B.
Donoven
Donoven is an alternative spelling of the given name Donovan, which is of Irish origin and used as a masculine first name and surname.
-
C.
Dolgan
Dolgan is a Turkic language spoken primarily by the Dolgan people in northern Siberia, especially in Russia’s Taymyr Peninsula.
-
D.
Devorski
Devorski is a surname most notably associated with Paul Devorski, a former National Hockey League referee.
-
E.
Baníkov
Baníkov is a prominent peak in Slovakia’s Western Tatras, popular with hikers for its rugged ridges and panoramic alpine views.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de610aa434819096671c5aabb9134a |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdf0ed0a88190a7126887364fccdd |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 10:23 p.m.