Triple

T14818388
Position Surface form Disambiguated ID Type / Status
Subject Zagyva River E348378 entity
Predicate mouthLocation P417 FINISHED
Object Szolnok E284469 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: Szolnok | Statement: [Zagyva River, mouthLocation, Szolnok]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Szolnok
Context triple: [Zagyva River, mouthLocation, Szolnok]
  • A. Szolnok chosen
    Szolnok is a city in central Hungary known as an important regional industrial and transportation hub along the Tisza River.
  • B. Kaposvár
    Kaposvár is a city in southwestern Hungary that serves as the administrative and cultural center of Somogy County.
  • C. Veszprém
    Veszprém is a historic city in western Hungary known for its medieval castle district and role as a regional cultural and administrative center.
  • D. Kalocsa
    Kalocsa is a historic town in southern Hungary known as an important Roman Catholic archiepiscopal center and for its traditional paprika production and folk art.
  • E. Szekszárd
    Szekszárd is a historic Hungarian town renowned as one of the country’s leading red wine regions and the administrative center of Tolna County.
  • 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_69d822eb8f588190bf53445e730a934f completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69decfe4cf38819090f25ef045351d5d completed April 14, 2026, 11:38 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa929b0b88190ad40d54ba4ef478a completed May 9, 2026, 9:37 p.m.
Created at: April 10, 2026, 1:50 a.m.