Triple

T20959708
Position Surface form Disambiguated ID Type / Status
Subject Rudnik Mountains E516203 entity
Predicate hasSettlement P1068 FINISHED
Object Rudnik (village) 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: Rudnik (village) | Statement: [Rudnik Mountains, hasSettlement, Rudnik (village)]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rudnik (village)
Context triple: [Rudnik Mountains, hasSettlement, Rudnik (village)]
  • A. Rudnik (settlement) chosen
    Rudnik is a settlement located in the Rudnik Mountains, known historically for its mining activities and mountainous surroundings.
  • B. Rudniki
    Rudniki is a village in southwestern Poland located within the Opole Voivodeship.
  • C. Lyudinovo
    Lyudinovo is an industrial town in western Russia known for its engineering and manufacturing sectors.
  • D. Nowa Ruda
    Nowa Ruda is a town in southwestern Poland, in the Lower Silesian Voivodeship, known for its historical coal mining industry and picturesque setting in the Owl Mountains.
  • E. Nikiforovo
    Nikiforovo is a village located in the mountainous Mavrovo region of North Macedonia, known for its proximity to Mavrovo National Park and Lake Mavrovo.
  • 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_69e0b4fde6c48190af1398e7e734629e completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fb6e50988190a564d2aaf1a9bc54 completed April 21, 2026, 4:22 a.m.
Created at: April 16, 2026, 1:30 p.m.