Triple
T19579292
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beránek |
E489943
|
entity |
| Predicate | transliteration |
P2508
|
FINISHED |
| Object | Beranek |
—
|
NE NERFINISHED |
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: Beranek | Statement: [Beránek, transliteration, Beranek]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Beranek Context triple: [Beránek, transliteration, Beranek]
-
A.
Beranek
chosen
Beranek is a surname most notably associated with Leo Beranek, an American acoustics expert and co-founder of the engineering firm Bolt, Beranek and Newman (BBN).
-
B.
Brunonek
Brunonek is a Polish diminutive form of the male given name Brunon, typically used as an affectionate or familiar nickname.
-
C.
Bonger
Bonger is a Dutch surname most notably associated with Johanna van Gogh-Bonger, the key figure in preserving and promoting Vincent van Gogh’s artistic legacy.
-
D.
Bochner
Bochner is a surname most notably associated with Salomon Bochner, a prominent mathematician known for his contributions to analysis and probability theory.
-
E.
Butzer
Butzer is a German surname most notably borne by the Protestant Reformer Martin Butzer (also known as Martin Bucer).
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402763b8819099e535979f094f9d |
completed | April 20, 2026, 3:03 p.m. |
Created at: April 10, 2026, 1:42 p.m.