Triple

T10656578
Position Surface form Disambiguated ID Type / Status
Subject Randenbroek E251103 entity
Predicate hasDutchName P744 FINISHED
Object Randenbroek E251103 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: Randenbroek | Statement: [Randenbroek, hasDutchName, Randenbroek]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Randenbroek
Context triple: [Randenbroek, hasDutchName, Randenbroek]
  • A. Randenbroek chosen
    Randenbroek is a historic estate near Amersfoort in the Netherlands, known as the place where the Dutch Golden Age architect and painter Jacob van Campen spent his final years.
  • B. Zuidbroek
    Zuidbroek is a village in the province of Groningen in the northeastern Netherlands, known historically as a small canal-side settlement in a largely rural landscape.
  • C. Bezuidenhout
    Bezuidenhout is a neighborhood in The Hague, Netherlands, known for its residential character and proximity to major government and business districts.
  • D. Groesbeek
    Groesbeek is a village in the Dutch province of Gelderland, known for its hilly landscape, World War II history, and wine production.
  • E. Rozenburg
    Rozenburg is a village in the municipality of Haarlemmermeer in the province of North Holland, 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_69d6aa5a4c4881908f39be6efe5981e5 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6dffa73a08190bf661df600b4ab96 completed April 8, 2026, 11:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69d98857ec248190bb655d36981a000a completed April 10, 2026, 11:31 p.m.
Created at: April 8, 2026, 9:07 p.m.