Triple
T17116588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prešov District |
E415353
|
entity |
| Predicate | namedAfter |
P63
|
FINISHED |
| Object | city of Prešov |
E83895
|
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: city of Prešov | Statement: [Prešov District, namedAfter, city of Prešov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: city of Prešov Context triple: [Prešov District, namedAfter, city of Prešov]
-
A.
Prešov
chosen
Prešov is a historic city in eastern Slovakia known for its preserved medieval center and role as a regional cultural and economic hub.
-
B.
Prešporok
Prešporok is the historical Slovak name for the city now known as Bratislava, the capital of Slovakia.
-
C.
Prešov District
Prešov District is an administrative district in eastern Slovakia that includes the city of Prešov and its surrounding municipalities.
-
D.
Považská Bystrica
Považská Bystrica is a town in northwestern Slovakia known as an industrial center situated in a valley surrounded by the Strážov Mountains.
-
E.
Town Hall of Prešov
The Town Hall of Prešov is a historic municipal building in the Slovak city of Prešov, notable for its architectural heritage and role as a cultural and administrative center.
- 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e80660048190832d8f91415dd7d7 |
completed | April 18, 2026, 8:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a013a0b69108190ba3ba6ba7f8d3935 |
completed | May 11, 2026, 2:08 a.m. |
Created at: April 10, 2026, 5:35 a.m.