Triple

T11952861
Position Surface form Disambiguated ID Type / Status
Subject Szolnok E284469 entity
Predicate locatedOnRiver P165 FINISHED
Object Tisza River E37143 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: Tisza River | Statement: [Szolnok, locatedOnRiver, Tisza River]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tisza River
Context triple: [Szolnok, locatedOnRiver, Tisza River]
  • A. Tisza chosen
    The Tisza is one of Central Europe's significant rivers, flowing through several countries including Hungary before joining the Danube.
  • B. 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.
  • C. Zala River
    The Zala River is a major river in western Hungary that drains a large catchment area before emptying into Lake Balaton.
  • D. Kapós River
    The Kapós River is a watercourse in southwestern Hungary that flows through the Transdanubian region before joining the Sió River.
  • E. 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.
  • 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_69d6ab2db38c8190b1f0ed6663ef8ada completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d90365da288190a132703df563de23 completed April 10, 2026, 2:04 p.m.
NED1 Entity disambiguation (via context triple) batch_69f62a76b0a48190800c5b3cc40308f3 completed May 2, 2026, 4:46 p.m.
Created at: April 8, 2026, 9:45 p.m.