Triple

T18724988
Position Surface form Disambiguated ID Type / Status
Subject Sárvár E457876 entity
Predicate locatedOn P40 FINISHED
Object River Rába 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: River Rába | Statement: [Sárvár, locatedOn, River Rába]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: River Rába
Context triple: [Sárvár, locatedOn, River Rába]
  • A. Kapós River
    The Kapós River is a watercourse in southwestern Hungary that flows through the Transdanubian region before joining the Sió River.
  • B. Rába River chosen
    The Rába River is a Central European waterway flowing from Austria through western Hungary, historically significant as a strategic site in various military conflicts.
  • C. Belá River
    The Belá River is a mountain river in northern Slovakia, known for its scenic course through the High Tatras region and popularity for rafting and outdoor recreation.
  • D. Sajó River
    The Sajó River is a waterway in Central Europe, chiefly in present-day Hungary and Slovakia, historically notable as the site of the Mongol victory over the Kingdom of Hungary at the 1241 Battle of Mohi.
  • E. Zala River
    The Zala River is a major river in western Hungary that drains a large catchment area before emptying into Lake Balaton.
  • 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_69d8d393ba9c8190a8b03b04ddbb0a09 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e56d72d2c4819080b0d31860976b5e completed April 20, 2026, 12:04 a.m.
Created at: April 10, 2026, 11:50 a.m.