Triple

T7000671
Position Surface form Disambiguated ID Type / Status
Subject Mazurek Dąbrowskiego E162328 entity
Predicate mentions P831 FINISHED
Object Czarniecki E175220 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: Czarniecki | Statement: [Mazurek Dąbrowskiego, mentions, Czarniecki]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Czarniecki
Context triple: [Mazurek Dąbrowskiego, mentions, Czarniecki]
  • A. Czarniecki chosen
    Czarniecki refers to Stefan Czarniecki, a 17th-century Polish military commander and national hero celebrated for his role in defending the Polish–Lithuanian Commonwealth, notably during the Swedish Deluge.
  • B. Korzeniowski
    Korzeniowski is a Polish surname most notably borne by contemporary film and television composer Abel Korzeniowski.
  • C. Zawisza
    Zawisza is a Polish surname historically associated with several notable figures, including nobles, politicians, and cultural personalities.
  • D. Czeremcha
    Czeremcha is a village in northeastern Poland that serves as a local railway junction and border-area transport hub near Belarus.
  • E. Tadeusz
    Tadeusz is a masculine given name of Slavic origin, particularly common in Poland.
  • 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_69c68857ffc08190857dc62cd5253777 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dc0f8830819091f4356296234713 completed March 27, 2026, 7:35 p.m.
NED1 Entity disambiguation (via context triple) batch_69c76a310eb08190a0fc1de2814aea08 completed March 28, 2026, 5:42 a.m.
Created at: March 27, 2026, 2:33 p.m.