Triple

T6342324
Position Surface form Disambiguated ID Type / Status
Subject Koningslo E142657 entity
Predicate hasMunicipalAuthority P3379 FINISHED
Object City of Vilvoorde E26610 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: City of Vilvoorde | Statement: [Koningslo, hasMunicipalAuthority, City of Vilvoorde]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: City of Vilvoorde
Context triple: [Koningslo, hasMunicipalAuthority, City of Vilvoorde]
  • A. Vilvoorde chosen
    Vilvoorde is a city in the Flemish Region of Belgium, located just north of Brussels and known as part of the capital’s broader metropolitan area.
  • B. Tervuren
    Tervuren is a municipality in Flemish Brabant, Belgium, known for its historic park, royal connections, and the Royal Museum for Central Africa.
  • C. Bellebeek
    Bellebeek is a small stream in Belgium that serves as a right-bank tributary of the River Dender.
  • D. Schaerbeek
    Schaerbeek is a multicultural municipality in the Brussels-Capital Region of Belgium, known for its Art Nouveau architecture and urban character.
  • E. Roeselare
    Roeselare is a city in western Belgium known as an economic and commercial center in the province of West Flanders.
  • 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_69c8eed9b120819094d588637edc6190 completed March 29, 2026, 9:20 a.m.
Created at: March 22, 2026, 4:30 p.m.