Triple

T8434304
Position Surface form Disambiguated ID Type / Status
Subject David Dubinsky E199188 entity
Predicate familyName P18 FINISHED
Object Dubinsky E721521 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: Dubinsky | Statement: [David Dubinsky, familyName, Dubinsky]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dubinsky
Context triple: [David Dubinsky, familyName, Dubinsky]
  • A. Zaslofsky
    Zaslofsky is a surname most notably associated with Max Zaslofsky, an early star guard in the National Basketball Association.
  • B. Dombrowski
    Dombrowski is a surname most prominently associated with Dave Dombrowski, a longtime Major League Baseball executive known for leading multiple franchises to pennants and World Series titles.
  • C. Blaustein
    Blaustein is a municipality in the Alb-Donau district of Baden-Württemberg in southern Germany, situated near the city of Ulm.
  • D. Reznik chosen
    Reznik is a surname of likely Eastern European origin, often associated with Jewish and Slavic families and appearing in various transliterated forms such as Resnick.
  • E. Brodinski
    Brodinski is a French DJ and electronic music producer known for his dark, techno-influenced sound and role in shaping the modern French electronic and club scene.
  • 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_69ca8314cd6c8190a6b8c2a1096e18f3 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cbd1a74d948190abd76e7a6efb42ec completed March 31, 2026, 1:52 p.m.
NED1 Entity disambiguation (via context triple) batch_69ce1d71d9748190903ed97dde6d28f4 completed April 2, 2026, 7:40 a.m.
Created at: March 30, 2026, 6:07 p.m.