Triple

T13442921
Position Surface form Disambiguated ID Type / Status
Subject Mercedes Jellinek E320409 entity
Predicate familyName P18 FINISHED
Object Jellinek E320409 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: Jellinek | Statement: [Mercedes Jellinek, familyName, Jellinek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jellinek
Context triple: [Mercedes Jellinek, familyName, Jellinek]
  • A. Jellinek chosen
    Jellinek is a surname most notably associated with Mercedes Jellinek, the namesake and inspiration for the Mercedes automobile brand.
  • B. Blanka Jellinek
    Blanka Jellinek was a member of the Jellinek family, historically associated with the early development and naming of the Mercedes automobile brand.
  • C. Helene Jellinek
    Helene Jellinek was a member of the Jellinek family associated with the early history of the Mercedes automobile brand.
  • D. Johanna Jellinek
    Johanna Jellinek was a member of the Jellinek family, historically associated with the origins of the Mercedes automobile brand.
  • E. Mira Jellinek
    Mira Jellinek was a member of the Jellinek family associated with the early history of the Mercedes automobile brand, known primarily as the sister of Mercedes Jellinek.
  • 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_69d80761e6cc8190a90c844589998ecc completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbaee881888190811ddf01bc699864 completed April 12, 2026, 2:40 p.m.
NED1 Entity disambiguation (via context triple) batch_69f74621474c8190b96a8f8561451bed completed May 3, 2026, 12:57 p.m.
Created at: April 9, 2026, 9:40 p.m.