Triple
T15884933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morava river system |
E385167
|
entity |
| Predicate | majorRiver |
P165
|
FINISHED |
| Object | Nišava |
—
|
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: Nišava | Statement: [Morava river system, majorRiver, Nišava]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Nišava Context triple: [Morava river system, majorRiver, Nišava]
-
A.
Nišava
chosen
Nišava is a river in southeastern Europe that flows through Bulgaria and Serbia, passing the city of Niš before joining the South Morava River.
-
B.
Nišava Valley
Nišava Valley is a geographic region in southeastern Europe shaped by the course of the Nišava River, known for its strategic transport routes and surrounding mountainous landscapes.
-
C.
Morača
Morača is a major river in Montenegro that flows through the capital city of Podgorica before emptying into Lake Skadar.
-
D.
Moravica
Moravica is a river in central Serbia that serves as a significant left-bank tributary of the West Morava.
-
E.
Vrbas
Vrbas is a town and municipality in the Bačka region of northern Serbia, known as a local administrative, industrial, and transportation center.
- 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1561997bc8190a40e7d68defbbddd |
completed | April 16, 2026, 9:35 p.m. |
Created at: April 10, 2026, 4:51 a.m.