Triple

T5021421
Position Surface form Disambiguated ID Type / Status
Subject Kashubia E112858 entity
Predicate hasMajorTown P316 FINISHED
Object Chojnice E229417 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: Chojnice | Statement: [Kashubia, hasMajorTown, Chojnice]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chojnice
Context triple: [Kashubia, hasMajorTown, Chojnice]
  • A. Chojnice chosen
    Chojnice is a historic town in northern Poland known for its medieval architecture and role as a local cultural and economic center.
  • B. Ciechocinek
    Ciechocinek is a Polish spa town renowned for its historic saline graduation towers and therapeutic health resorts.
  • C. Ojców
    Ojców is a small village in southern Poland known as a gateway to the picturesque Ojców National Park in the Kraków-Częstochowa Upland.
  • D. Oleśnica
    Oleśnica is a historic town in southwestern Poland known for its Renaissance castle and well-preserved old town.
  • E. Czernichów
    Czernichów is a village in southern Poland that serves as the seat of its namesake rural administrative district within the Kraków metropolitan area.
  • 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_69bd4435c2f48190be593158cbfcf8a3 completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd73656edc8190b802ad38d9552b58 completed March 20, 2026, 4:18 p.m.
NED1 Entity disambiguation (via context triple) batch_69befe4abf2c81908946d4ab18b7273d completed March 21, 2026, 8:23 p.m.
Created at: March 20, 2026, 1:36 p.m.