Triple

T23025075
Position Surface form Disambiguated ID Type / Status
Subject rural gmina Rytwiany E573285 entity
Predicate administrativeCenter P1474 FINISHED
Object Rytwiany 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: Rytwiany | Statement: [rural gmina Rytwiany, administrativeCenter, Rytwiany]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rytwiany
Context triple: [rural gmina Rytwiany, administrativeCenter, Rytwiany]
  • A. Rytwiany chosen
    Rytwiany is a village in south-central Poland known for its historic monastery complex and role as a local administrative center.
  • B. Ryczówek
    Ryczówek is a village in southern Poland located within the administrative district of Gmina Klucze in Lesser Poland Voivodeship.
  • C. Krowodrza
    Krowodrza is a central district of Kraków, Poland, known for its mix of historic urban neighborhoods, academic institutions, and cultural venues.
  • D. Ryglice
    Ryglice is a small town in southern Poland known for its rural character and location in the historical region of Lesser Poland.
  • E. Wyry
    Wyry is a village and administrative district in southern Poland, located within the Silesian 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_69e245b821008190b0e09cb02092aae1 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1847c671c8190a8095051d8c3cf93 completed April 29, 2026, 4:09 a.m.
Created at: April 17, 2026, 3:52 p.m.