Triple
T16977886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Žehra |
E411859
|
entity |
| Predicate | hasHistoricRegion |
P5057
|
FINISHED |
| Object | Spiš |
E129227
|
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: Spiš | Statement: [Žehra, hasHistoricRegion, Spiš]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Spiš Context triple: [Žehra, hasHistoricRegion, Spiš]
-
A.
Spiš
chosen
Spiš is a historical region in northeastern Slovakia and southeastern Poland, known for its medieval towns, castles, and rich cultural heritage.
-
B.
Spišská Stará Ves
Spišská Stará Ves is a small town in northern Slovakia near the Polish border, known as a gateway to the Pieniny National Park and the Dunajec River rafting area.
-
C.
Spišská Nová Ves
Spišská Nová Ves is a town in eastern Slovakia known as a cultural and economic center of the Spiš region and as a gateway to the Slovak Paradise National Park.
-
D.
Spiš region
The Spiš region is a historical and cultural area in northeastern Slovakia known for its medieval towns, castles, and UNESCO-listed Spiš Castle complex.
-
E.
Spišský Hrhov
Spišský Hrhov is a Slovak village renowned for its successful social integration of Roma residents and innovative community development projects.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d184f2cc81908ac629c8f87696f8 |
completed | April 18, 2026, 6:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00d477f7ec81909f1f0243004c9050 |
completed | May 10, 2026, 6:54 p.m. |
Created at: April 10, 2026, 5:32 a.m.