Triple

T20355207
Position Surface form Disambiguated ID Type / Status
Subject Drava Statistical Region E496626 entity
Predicate containsSettlement P847 FINISHED
Object Ruše 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: Ruše | Statement: [Drava Statistical Region, containsSettlement, Ruše]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ruše
Context triple: [Drava Statistical Region, containsSettlement, Ruše]
  • A. Ruše chosen
    Ruše is a small town in northeastern Slovenia, situated along the Drava River at the foothills of the Pohorje mountain range.
  • B. Musina
    Musina is a northern South African town in Limpopo Province, known as a key border and transport hub near Zimbabwe and for its history of copper and iron ore mining.
  • C. Rušanj
    Rušanj is a suburban settlement of Belgrade, Serbia, located within the municipality of Čukarica.
  • D. Řepy
    Řepy is a residential district in the western part of Prague, Czech Republic, known for its large housing estates and proximity to major transport routes.
  • E. Rulice
    Rulice is a village in central Poland located within the administrative district of Gmina Bielawy in Łódź Voivodeship.
  • 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_69e0b4a3f7f48190b37f354574028ca6 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67853f10881908ecde94036804a8a completed April 20, 2026, 7:02 p.m.
Created at: April 16, 2026, 11:25 a.m.