Triple

T13715029
Position Surface form Disambiguated ID Type / Status
Subject van Egmond E328873 entity
Predicate hasNotableMember P304 FINISHED
Object George van Egmond E915334 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: George van Egmond | Statement: [van Egmond, hasNotableMember, George van Egmond]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: George van Egmond
Context triple: [van Egmond, hasNotableMember, George van Egmond]
  • A. George van Egmond chosen
    George van Egmond was a 16th-century Dutch nobleman and Catholic bishop from the influential House of Egmond, notably serving as Bishop of Utrecht.
  • B. Willem Drost
    Willem Drost was a Dutch Golden Age painter and etcher known for his Rembrandt-influenced biblical and historical scenes.
  • C. Willem Brakman
    Willem Brakman was a Dutch novelist known for his experimental, often surreal prose and significant contribution to postwar Dutch literature.
  • D. Jan van der Does
    Jan van der Does was a Dutch nobleman, poet, and military leader best known for organizing and leading the defense of Leiden during the Eighty Years' War.
  • E. Jurriaan de Jonge
    Jurriaan de Jonge is an individual notable enough to be specifically cited as a bearer of the Dutch surname "de Jonge."
  • 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_69fde15abe6c8190a6212861bbce790e completed May 8, 2026, 1:12 p.m.
Created at: April 9, 2026, 9:54 p.m.