Triple
T13715039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | van Egmond |
E328873
|
entity |
| Predicate | hasSurnameForm |
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: [van Egmond, hasSurnameForm, Van Egmond]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Van Egmond Context triple: [van Egmond, hasSurnameForm, Van Egmond]
-
A.
van Egmond
chosen
Van Egmond is a Dutch noble family name historically associated with influential aristocratic lineages in the Netherlands.
-
B.
Muntendam
Muntendam is a village in the Dutch province of Groningen, now administratively part of the municipality of Midden-Groningen.
-
C.
Boesinghe
Boesinghe is a village in West Flanders, Belgium, known for its proximity to key World War I battlefields along the Yser Front.
-
D.
Eemster
Eemster is a small village in the Dutch province of Drenthe, situated within the municipality of Westerveld.
-
E.
Lodewijck
Lodewijck is a Dutch given name, an older or variant spelling of Lodewijk, equivalent to the English name Louis.
- 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_69f79d56a90081908158dcf4ee061fb6 |
completed | May 3, 2026, 7:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.