Triple
T13675953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashley Zukerman |
E327877
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Zukerman |
E769238
|
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: Zukerman | Statement: [Ashley Zukerman, familyName, Zukerman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Zukerman Context triple: [Ashley Zukerman, familyName, Zukerman]
-
A.
Zukerman
chosen
Zukerman is the surname of renowned Israeli-American violinist, violist, and conductor Pinchas Zukerman.
-
B.
Zuckerman
Zuckerman is a surname most notably associated with American screenwriter, actor, and director Buck Henry.
-
C.
Reznik
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.
-
D.
Zylberman
Zylberman is a surname of likely Ashkenazi Jewish origin borne by individuals such as Bathsheba Zylberman.
-
E.
Zimerman
Zimerman is the surname of Krystian Zimerman, a renowned Polish classical pianist and conductor.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc65c04988190b675e6fb7241e53c |
completed | April 12, 2026, 4:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7943dbf748190b41abfe9d81d1427 |
completed | May 3, 2026, 6:30 p.m. |
Created at: April 9, 2026, 9:53 p.m.