Triple
T5570235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubertus van Mook |
E146180
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | van Mook |
E146180
|
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 Mook | Statement: [Hubertus van Mook, familyName, van Mook]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: van Mook Context triple: [Hubertus van Mook, familyName, van Mook]
-
A.
van Mook
chosen
Van Mook is the surname of Hubertus van Mook, a prominent Dutch colonial administrator who served as Lieutenant Governor-General of the Dutch East Indies during and after World War II.
-
B.
van Slingelandt
Van Slingelandt is a Dutch surname historically associated with a prominent political and administrative family in the Netherlands.
-
C.
Goudriaan
Goudriaan is a small village in the Dutch province of South Holland, known for its rural character and historic polder landscape.
-
D.
Van der Madeweg
Van der Madeweg is a metro station in Amsterdam that serves as a stop on the city's rapid transit network.
-
E.
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.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0204f0d288190b9d4884665ba9116 |
completed | March 22, 2026, 5:01 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0284bb71881908c0ac4ea2a302327 |
completed | March 22, 2026, 5:35 p.m. |
Created at: March 22, 2026, 3:37 p.m.