Triple

T21493703
Position Surface form Disambiguated ID Type / Status
Subject Johannes Hubertus van Mook E530300 entity
Predicate familyName P18 FINISHED
Object van Mook NE NERFINISHED

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: [Johannes Hubertus van Mook, familyName, van Mook]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: van Mook
Context triple: [Johannes 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. van Wijnbergen
    Van Wijnbergen is a Dutch surname associated with individuals such as Everdine Huberta van Wijnbergen.
  • D. van Hoften
    Van Hoften is the surname of James D. van Hoften, an American former NASA astronaut and aerospace engineer.
  • E. Goudriaan
    Goudriaan is a small village in the Dutch province of South Holland, known for its rural character and historic polder landscape.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0c45bd15481909fba5910765cdda2 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69e9ea567244819091863350fedae3ae completed April 23, 2026, 9:45 a.m.
Created at: April 16, 2026, 6:23 p.m.