Triple

T10047993
Position Surface form Disambiguated ID Type / Status
Subject Afrojack E207666 entity
Predicate familyName P18 FINISHED
Object van de Wall E240196 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 de Wall | Statement: [Afrojack, familyName, van de Wall]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: van de Wall
Context triple: [Afrojack, familyName, van de Wall]
  • A. Nick van de Wall chosen
    Nick van de Wall, better known as Afrojack, is a Dutch DJ and record producer recognized as one of the leading figures in contemporary electronic dance music.
  • B. van de Velde
    Van de Velde is a Dutch surname borne by several notable figures, including artists, designers, and writers from the Low Countries.
  • C. van Wijnbergen
    Van Wijnbergen is a Dutch surname associated with individuals such as Everdine Huberta van Wijnbergen.
  • D. van Heutsz
    Van Heutsz is a Dutch surname most prominently associated with Johannes Benedictus van Heutsz, a colonial military leader and Governor-General of the Dutch East Indies.
  • 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_69ca835ad0608190b7c80b292da004f5 completed March 30, 2026, 2:06 p.m.
NER Named-entity recognition batch_69cdcf664dd881908786fcd802bf10da completed April 2, 2026, 2:07 a.m.
NED1 Entity disambiguation (via context triple) batch_69d2828f3980819083d041f09e63d8e6 completed April 5, 2026, 3:41 p.m.
Created at: March 30, 2026, 8:56 p.m.