Triple

T11328070
Position Surface form Disambiguated ID Type / Status
Subject Leon Wasilewski E268274 entity
Predicate familyName P18 FINISHED
Object Wasilewski E887642 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: Wasilewski | Statement: [Leon Wasilewski, familyName, Wasilewski]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Wasilewski
Context triple: [Leon Wasilewski, familyName, Wasilewski]
  • A. Wasilewski chosen
    Wasilewski is a Polish surname, typically indicating familial or geographic origin and commonly found in Poland and among the Polish diaspora.
  • B. Korzeniowski
    Korzeniowski is a Polish surname most notably borne by contemporary film and television composer Abel Korzeniowski.
  • C. Wojciechowski
    Wojciechowski is a Polish surname most notably borne by Stanisław Wojciechowski, who served as President of Poland in the early 20th century.
  • D. Ogiński
    Ogiński is the surname of a prominent Polish–Lithuanian noble family best known for composer and statesman Michał Kleofas Ogiński.
  • E. Kowalik
    Kowalik is a Polish surname, likely of similar origin or family line to the surname Kowalski.
  • 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_69d6aacb1f0881908c84a349fd1be047 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e9e330008190b75490efde01dc59 completed April 9, 2026, 6:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69e52608b7348190875597513ca1a995 completed April 19, 2026, 6:59 p.m.
Created at: April 8, 2026, 9:32 p.m.