Triple
T12077074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexandra Sokoloff |
E287577
|
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: [Alexandra Sokoloff, familyName, Sokoloff]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Sokoloff Context triple: [Alexandra 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_69d6ab4846e081908ee7bbd66a6d3459 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9045ceeec81909427cae8972eed26 |
completed | April 10, 2026, 2:08 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f660f48881908d50bf27b0892953 |
completed | May 2, 2026, 1:04 p.m. |
Created at: April 8, 2026, 9:48 p.m.