Triple
T15912042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olomouc District |
E385872
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Uničov |
E1175632
|
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: Uničov | Statement: [Olomouc District, contains, Uničov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Uničov Context triple: [Olomouc District, contains, Uničov]
-
A.
Uničov
chosen
Uničov is a historic town in the Olomouc Region of the Czech Republic, known as one of the country’s oldest royal towns with a well-preserved medieval center.
-
B.
Udava
Udava is a river in eastern Slovakia that serves as a tributary of the Laborec River.
-
C.
Junkovac
Junkovac is a small settlement located within the municipality of Lazarevac in Serbia.
-
D.
Rušanj
Rušanj is a suburban settlement of Belgrade, Serbia, located within the municipality of Čukarica.
-
E.
Slanica
Slanica was a former Slovak village in the Orava region that was submerged during the creation of the Orava Reservoir, with only its church preserved on an island as a memorial.
- 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_69d86da686e4819097cbf3b1fc2d881d |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e156601c988190b9bd0cd75897651b |
completed | April 16, 2026, 9:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb05750ac81908860143f4ca26cc7 |
completed | May 9, 2026, 10:08 p.m. |
Created at: April 10, 2026, 4:52 a.m.