Triple
T18769125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sidney van den Bergh |
E458967
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | van den Bergh |
—
|
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: van den Bergh | Statement: [Sidney van den Bergh, familyName, van den Bergh]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: van den Bergh Context triple: [Sidney van den Bergh, familyName, van den Bergh]
-
A.
van den Bergh
chosen
Van den Bergh is a Dutch-origin surname borne by various notable individuals across fields such as politics, science, and the arts.
-
B.
van den Bogaerde
van den Bogaerde is the original Dutch family name of the British actor and writer Dirk Bogarde.
-
C.
van Wijnbergen
Van Wijnbergen is a Dutch surname associated with individuals such as Everdine Huberta van Wijnbergen.
-
D.
van de Velde
Van de Velde is a Dutch surname borne by several notable figures, including artists, designers, and writers from the Low Countries.
-
E.
van Amsberg
Van Amsberg is the German-origin noble family name associated with the Dutch royal family, including members such as Prince Constantijn of the Netherlands.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d867264819098ae35c9feab3bb4 |
completed | April 20, 2026, 2:20 a.m. |
Created at: April 10, 2026, 11:52 a.m.