Triple

T11244792
Position Surface form Disambiguated ID Type / Status
Subject Krosno County E266174 entity
Predicate namedAfter P63 FINISHED
Object Krosno E217525 NE FINISHED

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: [Krosno County, namedAfter, Krosno]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Krosno
Context triple: [Krosno County, namedAfter, 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. Kłodzko
    Kłodzko is a historic town in southwestern Poland known for its well-preserved medieval architecture and prominent hilltop fortress.
  • D. Kresowa
    Kresowa is the nickname of the Polish 5th Kresowa Infantry Division, a World War II unit of the Polish Armed Forces in the West composed largely of soldiers from the eastern borderlands (Kresy).
  • E. Świdnica
    Świdnica is a historic town in southwestern Poland known for its well-preserved medieval architecture and the UNESCO-listed Church of Peace.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d6aac7953c8190b82caf9d7640fdf9 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e91c045c81908a9024a8aee32f4d completed April 9, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69ef127eaf588190aaca151ee4022f3c completed April 27, 2026, 7:38 a.m.
Created at: April 8, 2026, 9:31 p.m.