Triple

T23219531
Position Surface form Disambiguated ID Type / Status
Subject Bóbrka E580847 entity
Predicate nearCity P350 FINISHED
Object Krosno 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: Krosno | Statement: [Bóbrka, nearCity, Krosno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krosno
Context triple: [Bóbrka, nearCity, Krosno]
  • A. Krosno chosen
    Krosno is a historic town in southeastern Poland known for its glassmaking industry and well-preserved old town.
  • B. Krosno Odrzańskie
    Krosno Odrzańskie is a small historic town in western Poland, located on the Oder River in the Lubusz Voivodeship.
  • C. Komorno
    Komorno is a small settlement that forms one of the administrative parts of the town of Blovice in the Czech Republic.
  • D. Zloczow
    Zloczow is the historical Polish name for the town now known as Zolochiv, located in western Ukraine.
  • E. Kłodzko
    Kłodzko is a historic town in southwestern Poland known for its well-preserved medieval architecture and prominent hilltop fortress.
  • 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_69e2460389408190be74f41d217799a9 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f191675de48190858907872a065c56 completed April 29, 2026, 5:04 a.m.
Created at: April 17, 2026, 4:08 p.m.