Triple

T16805783
Position Surface form Disambiguated ID Type / Status
Subject Dukenburg district E408477 entity
Predicate contains P35 FINISHED
Object Meijhorst NE NERFINISHED

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: Meijhorst | Statement: [Dukenburg district, contains, Meijhorst]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Meijhorst
Context triple: [Dukenburg district, contains, Meijhorst]
  • A. Meijhorst chosen
    Meijhorst is a residential neighborhood in the Dukenburg district of Nijmegen in the Netherlands.
  • B. Zwanenburg
    Zwanenburg is a village in North Holland, Netherlands, situated near Amsterdam and known as a suburban residential community within the Haarlemmermeer municipality.
  • C. Goudswaard
    Goudswaard is a small village in the Dutch province of South Holland, known for its rural character and location on the island of Hoeksche Waard.
  • D. Steenbergen
    Steenbergen is a municipality and town in the Dutch province of North Brabant, known for its rural landscape and proximity to several major waterways.
  • E. Steenbergen
    Steenbergen is a small village located in the municipality of Noordenveld in the Dutch province of Drenthe.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d88393905081908d00a86b99996ac8 completed April 10, 2026, 4:58 a.m.
NER Named-entity recognition batch_69e3b2cc25dc81909443b2c83155267a completed April 18, 2026, 4:35 p.m.
Created at: April 10, 2026, 5:22 a.m.