Triple

T20231414
Position Surface form Disambiguated ID Type / Status
Subject Piekarski E495534 entity
Predicate hasPluralForm P5088 FINISHED
Object Piekarscy 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: Piekarscy | Statement: [Piekarski, hasPluralForm, Piekarscy]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Piekarscy
Context triple: [Piekarski, hasPluralForm, Piekarscy]
  • A. Piekarski chosen
    Piekarski is a Polish surname, typically derived from occupational or locational roots, borne by various individuals of Polish origin.
  • B. Piekary
    Piekary is a former settlement in southern Poland that became part of the modern city of Piekary Śląskie through an administrative merger.
  • C. Karwia
    Karwia is a seaside village on the Baltic coast of northern Poland, known for its wide sandy beaches and role as a popular summer resort.
  • D. Ryki
    Ryki is a small town in eastern Poland known for its location within the Lublin region and its local administrative and cultural role.
  • E. Prystaiko
    Prystaiko is the surname of Vadym Prystaiko, a Ukrainian diplomat and former Minister of Foreign Affairs.
  • 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_69da626cff80819097b530718a7c98b6 completed April 11, 2026, 3:02 p.m.
NER Named-entity recognition batch_69e66fddafac819089cef4158f5e0ab5 completed April 20, 2026, 6:26 p.m.
Created at: April 11, 2026, 11:39 p.m.