Triple

T21296092
Position Surface form Disambiguated ID Type / Status
Subject Belfry of Leuven E524925 entity
Predicate locatedIn P40 FINISHED
Object Leuven 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: Leuven | Statement: [Belfry of Leuven, locatedIn, Leuven]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Leuven
Context triple: [Belfry of Leuven, locatedIn, Leuven]
  • A. Leuven chosen
    Leuven is a historic Belgian city known for hosting KU Leuven, one of Europe’s leading research universities, and for its vibrant academic and cultural life.
  • B. Vilvoorde
    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.
  • C. Mechelen
    Mechelen is a historic city in the Flemish region of Belgium, known for its rich architectural heritage, medieval center, and prominent role in the Low Countries’ political and religious history.
  • D. Tervuren
    Tervuren is a municipality in Flemish Brabant, Belgium, known for its historic park, royal connections, and the Royal Museum for Central Africa.
  • E. Hasselt
    Hasselt is a historic small city in the Dutch province of Overijssel, known for its medieval center and canals.
  • 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_69e0b517e6748190850d6f6ddf323d69 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e7385858ec8190bdc9c5cdcb8d4507 completed April 21, 2026, 8:42 a.m.
Created at: April 16, 2026, 4:04 p.m.