Triple
T20500979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bratislava V District |
E503300
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Petržalka |
—
|
NE NERFINISHED |
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: Petržalka | Statement: [Bratislava V District, contains, Petržalka]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Petržalka Context triple: [Bratislava V District, contains, Petržalka]
-
A.
Petržalka
chosen
Petržalka is a densely populated borough of Bratislava, Slovakia, known for its extensive panel housing estates and location on the right bank of the Danube River.
-
B.
Nemešany
Nemešany is a small village and municipality in the Levoča District of the Prešov Region in eastern Slovakia.
-
C.
Piešťany
Piešťany is a Slovak spa town renowned for its thermal springs and health resorts, located on the Váh River.
-
D.
Púchov
Púchov is a town in northwestern Slovakia known for its industrial production and location on the Váh River.
-
E.
Pohronie
Pohronie is a historical and geographical region in central Slovakia situated along the Hron River.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4b1e52c8190894281cf7e3283ab |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e69cc1ea7081908d17c224b1670bd7 |
completed | April 20, 2026, 9:38 p.m. |
Created at: April 16, 2026, 11:35 a.m.