Triple

T11986387
Position Surface form Disambiguated ID Type / Status
Subject D. H. Th. Vollenhoven E285289 entity
Predicate givenName P17 FINISHED
Object Theodoor E270316 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: Theodoor | Statement: [D. H. Th. Vollenhoven, givenName, Theodoor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Theodoor
Context triple: [D. H. Th. Vollenhoven, givenName, Theodoor]
  • A. Teodoor chosen
    Teodoor is a given name variant of Theodore, typically used in certain European languages or contexts.
  • B. Adriaan
    Adriaan is a masculine given name of Dutch origin commonly used in the Netherlands and other Dutch-speaking regions.
  • C. Gerhardus
    Gerhardus is a masculine given name of Germanic origin, closely related to names like Gerhard and Gerard, typically meaning “strong with the spear” or “brave with the spear.”
  • D. Willem
    Willem is a given name, primarily used in Dutch-speaking regions, that corresponds to the English name William.
  • E. Constantijn
    Constantijn is a Dutch royal, the youngest son of former Queen Beatrix and brother of King Willem-Alexander 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_69d6ab44a77c8190a652f4b27164e4ef completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d903acbb9081908fe7f8360057785c completed April 10, 2026, 2:05 p.m.
NED1 Entity disambiguation (via context triple) batch_69f47237c23081909044388ff5dc73b3 completed May 1, 2026, 9:28 a.m.
Created at: April 8, 2026, 9:46 p.m.