Triple

T19944998
Position Surface form Disambiguated ID Type / Status
Subject Poprad valley E479399 entity
Predicate hasPart P35 FINISHED
Object Rytro 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: Rytro | Statement: [Poprad valley, hasPart, Rytro]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rytro
Context triple: [Poprad valley, hasPart, Rytro]
  • A. Rytro chosen
    Rytro is a village in southern Poland’s Lesser Poland Voivodeship, situated in the scenic Poprad Valley of the Western Carpathians and known as a local tourist and hiking destination.
  • B. Rohatyn
    Rohatyn is a historic town in western Ukraine known for its medieval roots and association with the Polish-Ukrainian noblewoman Roxelana (Hürrem Sultan).
  • C. Ryglice
    Ryglice is a small town in southern Poland known for its rural character and location in the historical region of Lesser Poland.
  • D. Morawa
    Morawa is a small rural town in Western Australia known for its grain farming, wildflower displays, and role as a service centre for the surrounding Mid West agricultural region.
  • E. Torysky
    Torysky is a small village and municipality located in the Levoča District of the Prešov Region in eastern Slovakia.
  • 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_69d8e522a17c819095165d4d24939fd8 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65a6654f481908089e1d66e17e024 completed April 20, 2026, 4:55 p.m.
Created at: April 10, 2026, 1:54 p.m.