Triple
T13715103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maximiliaan van Egmond |
E328875
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | van Egmond |
E328873
|
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 Egmond | Statement: [Maximiliaan van Egmond, familyName, van Egmond]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: van Egmond Context triple: [Maximiliaan van Egmond, familyName, van Egmond]
-
A.
van Egmond
chosen
Van Egmond is a Dutch noble family name historically associated with influential aristocratic lineages in the Netherlands.
-
B.
van Egeraat
van Egeraat is a Dutch surname most prominently associated with architect Erik van Egeraat.
-
C.
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.
-
D.
Van Stadensrus
Van Stadensrus is a small rural town in South Africa’s Free State province, situated within the Mangaung Metropolitan Municipality.
-
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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dd43973cf08190a417d0cca9dd314a |
completed | April 13, 2026, 7:27 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7b0676e50819085fe48f86c0f93d8 |
completed | May 3, 2026, 8:30 p.m. |
Created at: April 9, 2026, 9:54 p.m.