Triple

T8634974
Position Surface form Disambiguated ID Type / Status
Subject Wincenty Witos E204499 entity
Predicate familyName P18 FINISHED
Object Witos E204499 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: Witos | Statement: [Wincenty Witos, familyName, Witos]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Witos
Context triple: [Wincenty Witos, familyName, Witos]
  • A. Witos chosen
    Witos is a Polish surname most notably borne by Wincenty Witos, a prominent early 20th-century Polish politician and three-time Prime Minister.
  • B. Grósz
    Grósz is a Hungarian surname most notably borne by Károly Grósz, a late-20th-century Hungarian communist politician and former Prime Minister.
  • C. Kowalik
    Kowalik is a Polish surname, likely of similar origin or family line to the surname Kowalski.
  • D. Wachlarz
    Wachlarz was a Polish World War II underground diversionary unit that conducted sabotage and intelligence operations, particularly in the eastern territories occupied by Nazi Germany.
  • E. Wiktor
    Wiktor is a masculine given name, primarily used in Slavic countries, that corresponds to the name Victor.
  • 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_69ca834b903c8190add96cc651e1a477 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cc475fb9dc8190bd0d6e5edd05ea79 completed March 31, 2026, 10:14 p.m.
NED1 Entity disambiguation (via context triple) batch_69cebc1b330c81909ff8a6806401dfd1 completed April 2, 2026, 6:57 p.m.
Created at: March 30, 2026, 6:27 p.m.