Triple

T10274194
Position Surface form Disambiguated ID Type / Status
Subject Kassa E240920 entity
Predicate locatedOnRiver P165 FINISHED
Object Hornád River E240919 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: Hornád River | Statement: [Kassa, locatedOnRiver, Hornád River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hornád River
Context triple: [Kassa, locatedOnRiver, Hornád River]
  • A. Hornád River chosen
    The Hornád River is a Central European river flowing through eastern Slovakia and northeastern Hungary, passing major cities such as Košice before joining the Slaná/Sajó River.
  • B. Hron River
    The Hron River is a major river in central Slovakia that flows through mountainous regions including the Low Tatras before joining the Danube.
  • C. Holitna River
    The Holitna River is a remote river in southwestern Alaska known for its rich wildlife habitat and importance to local subsistence communities.
  • D. Svitava River
    The Svitava River is a significant river in the eastern Czech Republic that flows through cities such as Brno before joining the Svratka River.
  • E. Váh River
    The Váh River is the longest river in Slovakia, flowing from the Tatra Mountains through much of the country before joining the Danube.
  • 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_69d381a94c1881908fc38fc263d9b9c2 completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d4d28a9c508190824867c04e8dcbe7 completed April 7, 2026, 9:46 a.m.
NED1 Entity disambiguation (via context triple) batch_69d87e40205c8190a4788e1db1f149d2 completed April 10, 2026, 4:36 a.m.
Created at: April 6, 2026, 11:36 a.m.