Triple

T20936690
Position Surface form Disambiguated ID Type / Status
Subject Kartuzy County E515602 entity
Predicate hasMajorTown P316 FINISHED
Object Kartuzy 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: Kartuzy | Statement: [Kartuzy County, hasMajorTown, Kartuzy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kartuzy
Context triple: [Kartuzy County, hasMajorTown, Kartuzy]
  • A. Kartuzy chosen
    Kartuzy is a town in northern Poland that serves as the main cultural center of the Kashubian ethnic group.
  • B. Giżycko
    Giżycko is a popular lakeside town in northeastern Poland, known as a major sailing and tourism center in the Masurian Lake District.
  • C. Wawer
    Wawer is a district in southeastern Warsaw, Poland, historically known as the site of a notorious World War II Nazi massacre of Polish civilians.
  • D. Kwidzyn
    Kwidzyn is a historic town in northern Poland known for its medieval Teutonic castle complex and Gothic cathedral.
  • E. Tczew
    Tczew is a historic town in northern Poland on the Vistula River, known for its important railway bridges and role as a regional transport hub.
  • 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_69e0b4fc13408190b06868df03c5c29b completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6f9527004819082b72bf15e3c6419 completed April 21, 2026, 4:13 a.m.
Created at: April 16, 2026, 12:49 p.m.