Triple
T20712622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Silbermann |
E509085
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Silbermann |
—
|
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: Silbermann | Statement: [Ben Silbermann, familyName, Silbermann]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Silbermann Context triple: [Ben Silbermann, familyName, Silbermann]
-
A.
Silbermann
chosen
Silbermann is a German-language surname borne by various notable individuals, often associated with Central European heritage and culture.
-
B.
Sponsheim
Sponsheim is a district or locality within the town of Bingen am Rhein in Rhineland-Palatinate, Germany.
-
C.
Hammann
Hammann is a German-origin surname borne by various notable individuals in fields such as aviation, music, and academia.
-
D.
Stottlemeyer
Stottlemeyer is the surname of Captain Leland Stottlemeyer, a central police character from the television series "Monk."
-
E.
Fischmann
Fischmann is a surname variant of Fishman, typically of Ashkenazi Jewish origin.
- 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_69e0b4c40ad88190b81f77695366d328 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c1ce84e48190922db93ed4b5d21b |
completed | April 21, 2026, 12:16 a.m. |
Created at: April 16, 2026, 12:15 p.m.