Triple
T11704067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felvidék |
E278196
|
entity |
| Predicate | containsHistoricalCity |
P43430
|
FINISHED |
| Object | Selmecbánya |
E1024732
|
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: Selmecbánya | Statement: [Felvidék, containsHistoricalCity, Selmecbánya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Selmecbánya Context triple: [Felvidék, containsHistoricalCity, Selmecbánya]
-
A.
Selmecbánya
chosen
Selmecbánya is the historical Hungarian name for Banská Štiavnica, a renowned medieval mining town and UNESCO World Heritage site in present-day central Slovakia.
-
B.
Besztercebánya
Besztercebánya is a historic mining and cultural city in central Slovakia, known in Hungarian as Besztercebánya and in Slovak as Banská Bystrica.
-
C.
Bonyhád
Bonyhád is a town in southern Hungary known as an important local center within Tolna County.
-
D.
Mátészalka
Mátészalka is a town in northeastern Hungary known as a local administrative and economic center within the Northern Great Plain region.
-
E.
Tihany
Tihany is a historic village on the northern shore of Lake Balaton in Hungary, renowned for its Benedictine abbey, scenic peninsula, and traditional architecture.
- 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_69d6aaff2ce88190b4a1e4b341ad5377 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a49b1080819096593733ee48a187 |
completed | April 10, 2026, 7:19 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f739644ed48190896d7b2b6c3b5f8f |
completed | May 3, 2026, 12:02 p.m. |
Created at: April 8, 2026, 9:40 p.m.