Triple
T5494074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mel Brooks |
E123770
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Kaminsky |
E485979
|
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: Kaminsky | Statement: [Mel Brooks, familyName, Kaminsky]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kaminsky Context triple: [Mel Brooks, familyName, Kaminsky]
-
A.
Kaminsky
chosen
Kaminsky is the original family surname of American entertainer Danny Kaye, born David Daniel Kaminsky.
-
B.
Kamensky
Kamensky is a Russian surname most notably associated with former professional ice hockey player Valeri Kamensky.
-
C.
Joffe
Joffe is a surname most notably associated with Adolf Joffe, a prominent early 20th-century Russian revolutionary and diplomat.
-
D.
Rothkowitz
Rothkowitz is the original family surname of the abstract expressionist painter Mark Rothko, reflecting his Eastern European Jewish heritage.
-
E.
Zaslofsky
Zaslofsky is a surname most notably associated with Max Zaslofsky, an early star guard in the National Basketball Association.
- 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_69bd464a2d908190869324ce176779c8 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9294ea9c8190b394a8528c385ee9 |
completed | March 20, 2026, 6:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf6c95ba008190ad61e1d31ae38d98 |
completed | March 22, 2026, 4:14 a.m. |
Created at: March 20, 2026, 2:10 p.m.