Triple
T11831402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trnava Region |
E281400
|
entity |
| Predicate | hasCity |
P316
|
FINISHED |
| Object | Piešťany |
E478805
|
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: Piešťany | Statement: [Trnava Region, hasCity, Piešťany]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Piešťany Context triple: [Trnava Region, hasCity, Piešťany]
-
A.
Piešťany
chosen
Piešťany is a Slovak spa town renowned for its thermal springs and health resorts, located on the Váh River.
-
B.
Banská Štiavnica
Banská Štiavnica is a historic Slovak mining town and UNESCO World Heritage Site known for its well-preserved medieval and Renaissance architecture and rich mining heritage.
-
C.
Banská Belá
Banská Belá is a historic village in central Slovakia known for its long-standing association with the region’s mining industry.
-
D.
Liptovský Hrádok
Liptovský Hrádok is a small Slovak town in the Liptov region, known for its historic castle complex and location near the Tatra Mountains.
-
E.
Prešporok
Prešporok is the historical Slovak name for the city now known as Bratislava, the capital of Slovakia.
- 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a62c95988190a45dbaa7001c8846 |
completed | April 10, 2026, 7:26 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f79d2da6b48190bdd974fa9520bc87 |
completed | May 3, 2026, 7:08 p.m. |
Created at: April 8, 2026, 9:43 p.m.