Triple
T16933181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Feldman |
E410762
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Feldman |
E428082
|
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: Feldman | Statement: [Ben Feldman, familyName, Feldman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Feldman Context triple: [Ben Feldman, familyName, Feldman]
-
A.
Feldman
chosen
Feldman is a surname of Germanic and Ashkenazi Jewish origin borne by various notable individuals across fields such as music, academia, and the arts.
-
B.
Feidman
Feidman is the surname of Giora Feidman, an Argentine-Israeli clarinetist renowned for his interpretations of klezmer and Jewish soul music.
-
C.
Rubenfeld
Rubenfeld is a surname most notably associated with American actor and comedian Paul Reubens, best known for creating and portraying the character Pee-wee Herman.
-
D.
Furthman
Furthman is a surname most notably associated with American screenwriter Jules Furthman, known for his work on classic Hollywood films.
-
E.
Futterman
Futterman is a surname most notably associated with American actor and screenwriter Dan Futterman.
- 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_69d886c886688190967be07322597ac9 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3cf2650e08190b669d0cf2cf1275b |
completed | April 18, 2026, 6:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00cfe0ff608190903d0e64e04b1550 |
completed | May 10, 2026, 6:35 p.m. |
Created at: April 10, 2026, 5:30 a.m.