Triple

T13755302
Position Surface form Disambiguated ID Type / Status
Subject Luis van Rooten E330459 entity
Predicate familyName P18 FINISHED
Object van Rooten E330459 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 Rooten | Statement: [Luis van Rooten, familyName, van Rooten]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: van Rooten
Context triple: [Luis van Rooten, familyName, van Rooten]
  • A. van Rooten chosen
    Van Rooten is the surname of Luis van Rooten, a Panamanian-born American character actor and voice artist known for his work in mid-20th-century film and radio.
  • B. van Wijnbergen
    Van Wijnbergen is a Dutch surname associated with individuals such as Everdine Huberta van Wijnbergen.
  • C. van Slingelandt
    Van Slingelandt is a Dutch surname historically associated with a prominent political and administrative family in the Netherlands.
  • D. van Eesteren
    Van Eesteren is a Dutch surname most notably associated with Cornelis van Eesteren, an influential modernist architect and urban planner.
  • E. van Riemsdijk
    Van Riemsdijk is a Dutch surname associated with several notable figures, including colonial administrators and scholars from 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_69d81c573f288190aa2403d484fa3d49 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de02179c948190a652cc8c586e418f completed April 14, 2026, 9 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7a859e6748190aa1899830a02b710 completed May 3, 2026, 7:56 p.m.
Created at: April 9, 2026, 10:09 p.m.