Triple

T20390460
Position Surface form Disambiguated ID Type / Status
Subject Mario F. Kassar E498069 entity
Predicate familyName P18 FINISHED
Object Kassar 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: Kassar | Statement: [Mario F. Kassar, familyName, Kassar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Kassar
Context triple: [Mario F. Kassar, familyName, Kassar]
  • A. Kassar chosen
    Kassar is a surname most notably associated with Mario F. Kassar, a prominent film producer known for major Hollywood action blockbusters.
  • B. Kassis
    Kassis is a family name of likely Levantine, particularly Palestinian or broader Arab, origin.
  • C. Kassir
    Kassir is a surname most notably associated with American actor and comedian John Kassir, known for voicing the Crypt Keeper in the television series "Tales from the Crypt."
  • D. Dugal
    Dugal is a masculine given name of Scottish origin, closely related to and often considered a variant of the name Dugald.
  • E. Raddai
    Raddai is a lesser-known biblical figure mentioned in the Old Testament as one of the sons in Jesse’s family line connected to King David.
  • 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_69e0b4a71ebc8190b153a36c738730f4 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6790f8d9c819093038f6bb6f47a92 completed April 20, 2026, 7:05 p.m.
Created at: April 16, 2026, 11:28 a.m.