Triple
T9724146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sam Jaffe |
E235558
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Jaffe |
E796367
|
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: Jaffe | Statement: [Sam Jaffe, familyName, Jaffe]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Jaffe Context triple: [Sam Jaffe, familyName, Jaffe]
-
A.
Jaffe
chosen
Jaffe is a surname most notably associated with American film producer Stanley R. Jaffe, known for his work on acclaimed movies such as "Kramer vs. Kramer."
-
B.
Joffe
Joffe is a surname most notably associated with Adolf Joffe, a prominent early 20th-century Russian revolutionary and diplomat.
-
C.
Feigel
Feigel is a surname of Germanic or Yiddish origin, often associated with Central and Eastern European Jewish families.
-
D.
Zaslofsky
Zaslofsky is a surname most notably associated with Max Zaslofsky, an early star guard in the National Basketball Association.
-
E.
Jeffe
Jeffe is an alternative spelling variant of the given name Jeff, typically used as a personal name.
- 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_69ca84d0123c819096f9dc3b6abb0881 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e77096481908ffd315fecb1d5ec |
completed | April 1, 2026, 10:38 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19faa064081909c1d23044984a17c |
completed | April 4, 2026, 11:32 p.m. |
Created at: March 30, 2026, 8:21 p.m.