Triple
T10521709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pieter M. van Alphen |
E248188
|
entity |
| Predicate | hasLastName |
P18
|
FINISHED |
| Object |
van Alphen
Van Alphen is a Dutch surname associated with various notable individuals in fields such as science, literature, and public life.
|
E868636
|
NE FINISHED |
How this triple was built (4 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 Alphen | Statement: [Pieter M. van Alphen, hasLastName, van Alphen]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: van Alphen Context triple: [Pieter M. van Alphen, hasLastName, van Alphen]
-
A.
van Almonde
Van Almonde is a Dutch noble family name most notably associated with Admiral Philips van Almonde, a prominent naval commander of the 17th-century Dutch Republic.
-
B.
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.
-
C.
De Haas
De Haas is a surname of Dutch origin, often associated with individuals and families in the Netherlands and abroad.
-
D.
van Dam
van Dam is a Dutch surname commonly associated with individuals of Dutch origin or ancestry.
-
E.
van Wijnbergen
Van Wijnbergen is a Dutch surname associated with individuals such as Everdine Huberta van Wijnbergen.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: van Alphen Triple: [Pieter M. van Alphen, hasLastName, van Alphen]
Generated description
Van Alphen is a Dutch surname associated with various notable individuals in fields such as science, literature, and public life.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: van Alphen Target entity description: Van Alphen is a Dutch surname associated with various notable individuals in fields such as science, literature, and public life.
-
A.
van Almonde
Van Almonde is a Dutch noble family name most notably associated with Admiral Philips van Almonde, a prominent naval commander of the 17th-century Dutch Republic.
-
B.
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.
-
C.
De Haas
De Haas is a surname of Dutch origin, often associated with individuals and families in the Netherlands and abroad.
-
D.
van Dam
van Dam is a Dutch surname commonly associated with individuals of Dutch origin or ancestry.
-
E.
van Wijnbergen
Van Wijnbergen is a Dutch surname associated with individuals such as Everdine Huberta van Wijnbergen.
- F. None of above. chosen
Provenance (5 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_69d381c5c7448190bec34bee7ec72bac |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d509dec25881909bc748640f26a416 |
completed | April 7, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d90e119fe4819085e5c1c6e71e6260 |
completed | April 10, 2026, 2:49 p.m. |
| NEDg | Description generation | batch_69d9107dc8448190998c4044f68a775e |
completed | April 10, 2026, 3 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d911e7d2dc8190a67b2513607fdf98 |
completed | April 10, 2026, 3:06 p.m. |
Created at: April 6, 2026, 12:29 p.m.