Triple
T11353093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jelšava |
E268882
|
entity |
| Predicate | formerName |
P65
|
FINISHED |
| Object | Jolsva |
E731522
|
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: Jolsva | Statement: [Jelšava, formerName, Jolsva]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jolsva Context triple: [Jelšava, formerName, Jolsva]
-
A.
Järla Sjö
Järla Sjö is a lake and residential area in the eastern suburbs of Stockholm, Sweden, known for its scenic waterfront setting within Nacka.
-
B.
Svaliava
chosen
Svaliava is a small town in western Ukraine known for its scenic Carpathian surroundings and mineral springs.
-
C.
Veddesta
Veddesta is an industrial and commercial area in Järfälla Municipality, northwest of central Stockholm, Sweden.
-
D.
Söll
Söll is a popular Austrian village and ski resort in the Kitzbühel Alps, known for its extensive winter sports facilities and scenic alpine setting.
-
E.
Sennevika
Sennevika is a small settlement located on the island of Senja in northern Norway, known for its coastal Arctic landscape.
- 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_69d6aacbe18081909e5fadb50082dd96 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7ea24489081908fbf47fd2e6d709c |
completed | April 9, 2026, 6:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e543a6e97481909dc77a553b217b4d |
completed | April 19, 2026, 9:05 p.m. |
Created at: April 8, 2026, 9:33 p.m.