Triple

T11703858
Position Surface form Disambiguated ID Type / Status
Subject Medzibodrožie E278191 entity
Predicate locatedBetween P1262 FINISHED
Object Bodrog River E234401 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: Bodrog River | Statement: [Medzibodrožie, locatedBetween, Bodrog River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bodrog River
Context triple: [Medzibodrožie, locatedBetween, Bodrog River]
  • 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. 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.
  • C. Szamos River
    The Szamos River is a Central European river flowing through Romania and Hungary, known for joining the Tisa River and draining part of the Eastern Carpathians.
  • D. Zala River
    The Zala River is a major river in western Hungary that drains a large catchment area before emptying into Lake Balaton.
  • E. Bodrog chosen
    Bodrog is a river in Central Europe that flows through Slovakia and Hungary before joining the Tisza River.
  • 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_69d6aaff2ce88190b4a1e4b341ad5377 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a49b1080819096593733ee48a187 completed April 10, 2026, 7:19 a.m.
NED1 Entity disambiguation (via context triple) batch_69f48a027dec8190aea103f0974186b0 completed May 1, 2026, 11:09 a.m.
Created at: April 8, 2026, 9:40 p.m.