Triple
T9896154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter van Dam |
E182177
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | van Dam |
E29567
|
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: van Dam | Statement: [Peter van Dam, familyName, van Dam]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: van Dam Context triple: [Peter van Dam, familyName, van Dam]
-
A.
van Dam
chosen
van Dam is a Dutch surname commonly associated with individuals of Dutch origin or ancestry.
-
B.
Vandamm
Vandamm is a surname, often a variant spelling of "van Damm," associated with various individuals in arts, entertainment, and other fields.
-
C.
Van der Madeweg
Van der Madeweg is a metro station in Amsterdam that serves as a stop on the city's rapid transit network.
-
D.
van Egmond
Van Egmond is a Dutch noble family name historically associated with influential aristocratic lineages in the Netherlands.
-
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 (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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4a9d2f4819086cfdd42b613cd8c |
completed | April 2, 2026, 12:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1eb1355888190baf9846815801e92 |
completed | April 5, 2026, 4:54 a.m. |
Created at: March 30, 2026, 8:39 p.m.