Triple
T12977693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olza River |
E321570
|
entity |
| Predicate | hasAlternativeSpelling |
P457
|
FINISHED |
| Object | Olše (Czech) |
E785944
|
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: Olše (Czech) | Statement: [Olza River, hasAlternativeSpelling, Olše (Czech)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Olše (Czech) Context triple: [Olza River, hasAlternativeSpelling, Olše (Czech)]
-
A.
Olše
chosen
Olše is a river in the eastern Czech Republic that flows through the Moravian-Silesian Region before joining the Oder.
-
B.
Třemešné
Třemešné is a small municipality and village in the Plzeň Region of the Czech Republic.
-
C.
Blatná
Blatná is a historic Czech town best known for its picturesque water castle and surrounding ponds in the South Bohemian countryside.
-
D.
Žužemberk
Žužemberk is a small historic town in southeastern Slovenia, known for its medieval castle and picturesque setting along the Krka River.
-
E.
Ostravice
Ostravice is a river in the Czech Republic that flows through the Moravian-Silesian region and gives its name to the town of Ostravice and partly to the city of Ostrava.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6b8f0315c8190aae5908ba65d5867 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 9, 2026, 8:38 p.m.