Triple
T16983757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suzanne Fleisher Roberts |
E412007
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Fleisher |
E770713
|
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: Fleisher | Statement: [Suzanne Fleisher Roberts, familyName, Fleisher]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Fleisher Context triple: [Suzanne Fleisher Roberts, familyName, Fleisher]
-
A.
Fleisher
chosen
Fleisher is a surname most notably associated with Leon Fleisher, the acclaimed American pianist and conductor.
-
B.
Finkelstein
Finkelstein is a Jewish surname of German and Yiddish origin, commonly associated with families of Central and Eastern European descent.
-
C.
Fischel
Fischel is the birth name of Fred Lebow, the Romanian-American founder and long-time director of the New York City Marathon.
-
D.
Fischmann
Fischmann is a surname variant of Fishman, typically of Ashkenazi Jewish origin.
-
E.
Fishel
Fishel is a surname most notably associated with American actress and television personality Danielle Fishel.
- 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_69d886ca8f348190812768ea8d5055ce |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d18a0bf881908c449f499eb86495 |
completed | April 18, 2026, 6:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00dc0f13c88190b55da5be40a0a476 |
completed | May 10, 2026, 7:27 p.m. |
Created at: April 10, 2026, 5:32 a.m.