Triple
T7189972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erik van Egeraat |
E167664
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | van Egeraat |
E167664
|
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 Egeraat | Statement: [Erik van Egeraat, familyName, van Egeraat]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: van Egeraat Context triple: [Erik van Egeraat, familyName, van Egeraat]
-
A.
van Egeraat
chosen
van Egeraat is a Dutch surname most prominently associated with architect Erik van Egeraat.
-
B.
van Egmond
Van Egmond is a Dutch noble family name historically associated with influential aristocratic lineages in the Netherlands.
-
C.
van Everdingen
van Everdingen is a Dutch surname most notably associated with the 17th-century landscape painter Allart van Everdingen.
-
D.
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.
-
E.
van Heutsz
Van Heutsz is a Dutch surname most prominently associated with Johannes Benedictus van Heutsz, a colonial military leader and Governor-General of the Dutch East Indies.
- 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_69c6888b5248819090499a884ee3ec39 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8ff1ad0819094761f8c73e3e986 |
completed | March 27, 2026, 8:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7b95c671c8190bf75b5807c6c320c |
completed | March 28, 2026, 11:19 a.m. |
Created at: March 27, 2026, 2:50 p.m.