Triple
T12305609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonkvrouw van Amsberg |
E293343
|
entity |
| Predicate | familyNameComponent |
P18
|
FINISHED |
| Object | van Amsberg |
E294249
|
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 Amsberg | Statement: [Jonkvrouw van Amsberg, familyNameComponent, van Amsberg]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: van Amsberg Context triple: [Jonkvrouw van Amsberg, familyNameComponent, van Amsberg]
-
A.
van Amsberg
chosen
Van Amsberg is the German-origin noble family name associated with the Dutch royal family, including members such as Prince Constantijn of the Netherlands.
-
B.
van Wijnbergen
Van Wijnbergen is a Dutch surname associated with individuals such as Everdine Huberta van Wijnbergen.
-
C.
van Swanenburg
Van Swanenburg is a Dutch family name historically associated with artists and notable figures from the Netherlands.
-
D.
van Riemsdijk
Van Riemsdijk is a Dutch surname associated with several notable figures, including colonial administrators and scholars from the Netherlands.
-
E.
van Slingelandt
Van Slingelandt is a Dutch surname historically associated with a prominent political and administrative family in 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f00695c8190b7365e4593631690 |
completed | April 10, 2026, 6:18 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f61e7f8fd08190bdef3bb761d53f97 |
completed | May 2, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:53 p.m.