Triple

T12421257
Position Surface form Disambiguated ID Type / Status
Subject Eleanor Sokoloff E296776 entity
Predicate familyName P18 FINISHED
Object Sokoloff E287577 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: Sokoloff | Statement: [Eleanor Sokoloff, familyName, Sokoloff]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sokoloff
Context triple: [Eleanor Sokoloff, familyName, Sokoloff]
  • A. Sokoloff chosen
    Sokoloff is a Russian-origin surname borne by various notable individuals in fields such as music, literature, and politics.
  • B. Sokolovsky
    Sokolovsky is a Russian surname most notably associated with Soviet military commander Vasily Sokolovsky.
  • C. Sokolow
    Sokolow is a Jewish surname most notably associated with Nahum Sokolow, a prominent Zionist leader, author, and translator of the late 19th and early 20th centuries.
  • D. Zaslofsky
    Zaslofsky is a surname most notably associated with Max Zaslofsky, an early star guard in the National Basketball Association.
  • E. Poliakoff
    Poliakoff is a surname most notably associated with British playwright and director Stephen Poliakoff.
  • 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_69d6ada0640c81908c061d7fb3d47786 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d702b1481909db5f5bed6292ce0 completed April 10, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6349552fc81909fe73dea082e3a25 completed May 2, 2026, 5:29 p.m.
Created at: April 8, 2026, 9:55 p.m.