Triple
T22985465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tvrdošín District |
E571593
|
entity |
| Predicate | locatedOnRiver |
P165
|
FINISHED |
| Object | Orava River |
—
|
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: Orava River | Statement: [Tvrdošín District, locatedOnRiver, Orava River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Orava River Context triple: [Tvrdošín District, locatedOnRiver, Orava River]
-
A.
Orava River
chosen
The Orava River is a significant river in northern Slovakia that flows through the Orava region before joining the Váh River.
-
B.
Bystrica River
The Bystrica River is a Slovak river that flows through central Slovakia and joins the Hron River as one of its notable tributaries.
-
C.
Žitava River
The Žitava River is a river in southern Slovakia that flows through the Danubian Lowland before joining the Nitra River.
-
D.
Silnica River
The Silnica River is a small river in south-central Poland that flows through the city of Kielce and forms part of its urban landscape and recreation areas.
-
E.
Orava
Orava is a historical region in northern Slovakia and southern Poland, known for its mountainous landscapes, traditional villages, and the prominent Orava Castle.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182996ee08190ab74014ee7ecac2b |
completed | April 29, 2026, 4:01 a.m. |
Created at: April 17, 2026, 3:49 p.m.