Triple

T6342117
Position Surface form Disambiguated ID Type / Status
Subject Arrondissement of Halle-Vilvoorde E142651 entity
Predicate hasMunicipality P847 FINISHED
Object Opwijk
Opwijk is a municipality in the Flemish Brabant province of Belgium, situated in the Dutch-speaking region of Flanders.
E586234 NE FINISHED

How this triple was built (4 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: Opwijk | Statement: [Arrondissement of Halle-Vilvoorde, hasMunicipality, Opwijk]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Opwijk
Context triple: [Arrondissement of Halle-Vilvoorde, hasMunicipality, Opwijk]
  • A. Zijdelwaard
    Zijdelwaard is a residential neighborhood in the town of Uithoorn in the province of North Holland, Netherlands.
  • B. Noordwyk
    Noordwyk is a residential suburb located within the Midrand area of Johannesburg, South Africa.
  • C. Wijhe
    Wijhe is a village in the Dutch province of Overijssel, known as a historic settlement along the river IJssel.
  • D. Nissewaard
    Nissewaard is a municipality and town in the western Netherlands, located on the island of Voorne-Putten in the province of South Holland.
  • E. Boskoop
    Boskoop is a Dutch town historically renowned as a major center of tree and nursery cultivation.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Opwijk
Triple: [Arrondissement of Halle-Vilvoorde, hasMunicipality, Opwijk]
Generated description
Opwijk is a municipality in the Flemish Brabant province of Belgium, situated in the Dutch-speaking region of Flanders.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: Opwijk
Target entity description: Opwijk is a municipality in the Flemish Brabant province of Belgium, situated in the Dutch-speaking region of Flanders.
  • A. Zijdelwaard
    Zijdelwaard is a residential neighborhood in the town of Uithoorn in the province of North Holland, Netherlands.
  • B. Noordwyk
    Noordwyk is a residential suburb located within the Midrand area of Johannesburg, South Africa.
  • C. Wijhe
    Wijhe is a village in the Dutch province of Overijssel, known as a historic settlement along the river IJssel.
  • D. Nissewaard
    Nissewaard is a municipality and town in the western Netherlands, located on the island of Voorne-Putten in the province of South Holland.
  • E. Boskoop
    Boskoop is a Dutch town historically renowned as a major center of tree and nursery cultivation.
  • F. None of above. chosen

Provenance (5 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_69c008d5ab108190b346c465696824a9 completed March 22, 2026, 3:20 p.m.
NER Named-entity recognition batch_69c0674445748190bce2d638048be77c completed March 22, 2026, 10:03 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6043afb4081908d480ad868625909 completed March 27, 2026, 4:14 a.m.
NEDg Description generation batch_69c605eb80308190b2c2f0d1f35b060d completed March 27, 2026, 4:22 a.m.
NED2 Entity disambiguation (via description) batch_69c6065044908190b2ba71490a3bae54 completed March 27, 2026, 4:23 a.m.
Created at: March 22, 2026, 4:30 p.m.