Triple
T19542809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bratislava II District |
E488950
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Ostredky |
—
|
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: Ostredky | Statement: [Bratislava II District, contains, Ostredky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ostredky Context triple: [Bratislava II District, contains, Ostredky]
-
A.
Ostredky
chosen
Ostredky is a residential neighborhood within the Ružinov borough of Bratislava, Slovakia.
-
B.
Ostredok
Ostredok is the highest peak of the Veľká Fatra range in central Slovakia, known for its rounded grassy summit and panoramic views.
-
C.
Řepy
Řepy is a residential district in the western part of Prague, Czech Republic, known for its large housing estates and proximity to major transport routes.
-
D.
Poucet
Poucet is a village in the municipality of Hannut in the province of Liège, Belgium.
-
E.
Noznisky
Noznisky is a relatively uncommon family surname associated with individuals such as Shirley Marlin Noznisky.
- 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_69d8e8db5b6c8190984b61f91981f575 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6387442588190a2cdae60a6a940d6 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 10, 2026, 1:41 p.m.