Triple

T6342118
Position Surface form Disambiguated ID Type / Status
Subject Arrondissement of Halle-Vilvoorde E142651 entity
Predicate hasMunicipality P847 FINISHED
Object Overijse E241178 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: Overijse | Statement: [Arrondissement of Halle-Vilvoorde, hasMunicipality, Overijse]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Overijse
Context triple: [Arrondissement of Halle-Vilvoorde, hasMunicipality, Overijse]
  • A. Overijse chosen
    Overijse is a municipality in the Flemish Brabant province of Belgium, known for its green residential character and extensive vineyards.
  • B. Geervliet
    Geervliet is a small historic town in the western Netherlands, located in the province of South Holland.
  • C. Betuwe
    Betuwe is a fertile riverine region in the Dutch province of Gelderland, renowned for its extensive fruit orchards and scenic landscapes between the Rhine and Waal rivers.
  • D. Bollenstreek
    Bollenstreek is a coastal region in the western Netherlands famous for its extensive flower bulb fields and springtime tulip displays.
  • E. Maasbracht
    Maasbracht is a town in the Dutch province of Limburg, known as an inland port and industrial center along the River Meuse.
  • 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_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_69c93f988ab0819081e3b15bb7414c99 completed March 29, 2026, 3:04 p.m.
Created at: March 22, 2026, 4:30 p.m.