Triple

T9078511
Position Surface form Disambiguated ID Type / Status
Subject Oscar Lorkowski E217550 entity
Predicate familyName P18 FINISHED
Object Lorkowski E776432 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: Lorkowski | Statement: [Oscar Lorkowski, familyName, Lorkowski]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lorkowski
Context triple: [Oscar Lorkowski, familyName, Lorkowski]
  • A. Lorkowski chosen
    Lorkowski is a surname of likely Polish origin borne by individuals such as Joe Lorkowski.
  • B. Wolski
    Wolski is a Polish surname borne by various notable individuals in fields such as film, sports, and academia.
  • C. Mrugowsky
    Mrugowsky is a German surname most notably associated with Joachim Mrugowsky, an SS officer and physician involved in Nazi human experimentation during World War II.
  • D. Ludwik
    Ludwik is a given name, primarily used in Polish, that corresponds to the name Ludwig in other European languages.
  • E. Wojciechowski
    Wojciechowski is a Polish surname most notably borne by Stanisław Wojciechowski, who served as President of Poland in the early 20th century.
  • 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_69ca83d6c14c8190bc056d927f00a2a2 completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69cc95c7d3688190a4c1c6a92965eae4 completed April 1, 2026, 3:49 a.m.
NED1 Entity disambiguation (via context triple) batch_69d017baebb881908cfecd3438a17166 completed April 3, 2026, 7:40 p.m.
Created at: March 30, 2026, 7:12 p.m.