Triple
T19097145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nivy |
E467434
|
entity |
| Predicate | hasStreet |
P959
|
FINISHED |
| Object | Mlynské nivy |
—
|
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: Mlynské nivy | Statement: [Nivy, hasStreet, Mlynské nivy]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mlynské nivy Context triple: [Nivy, hasStreet, Mlynské nivy]
-
A.
Mlyny
Mlyny is a village in present-day Poland historically associated with Ukrainian cultural figures, including as the place where composer Mykhailo Verbytsky died.
-
B.
Mlynské nivy area
chosen
Mlynské nivy area is a central business and transport district in Bratislava known for its modern offices, bus station, and commercial developments.
-
C.
Velká Deštná
Velká Deštná is a prominent mountain in northeastern Bohemia, Czech Republic, known for its scenic views and popular hiking trails.
-
D.
Skalnaté pleso
Skalnaté pleso is a mountain lake in the High Tatras of Slovakia, known as a popular hiking and tourist destination surrounded by alpine scenery.
-
E.
Mokřiny
Mokřiny is a village and administrative part of the town of Aš in the Karlovy Vary Region of the Czech Republic.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e369aeac81908913c21f4c234c8e |
completed | April 20, 2026, 8:27 a.m. |
Created at: April 10, 2026, 12:04 p.m.