Triple
T11792103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jakub Berman |
E280412
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Berman |
E626263
|
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: Berman | Statement: [Jakub Berman, familyName, Berman]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Berman Context triple: [Jakub Berman, familyName, Berman]
-
A.
Berman
chosen
Berman is a surname of Ashkenazi Jewish origin borne by various notable individuals across fields such as art, politics, and academia.
-
B.
Berryman
Berryman is a surname most prominently associated with Guy Berryman, the Scottish bassist of the band Coldplay.
-
C.
Bromfman
Bromfman is a surname most notably associated with Brazilian composer and music producer Pedro Bromfman, known for his work on film and television scores.
-
D.
Erdman
Erdman is a masculine given name most notably borne by Disney story artist and screenwriter Erdman Penner.
-
E.
Lerman
Lerman is a surname most notably associated with American actor Logan Lerman, known for roles in films such as the "Percy Jackson" series and "The Perks of Being a Wallflower."
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a588d2c881909783c2d678c2a474 |
completed | April 10, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f09107fd2481908d765d2188035012 |
completed | April 28, 2026, 10:50 a.m. |
Created at: April 8, 2026, 9:42 p.m.