Triple

T21299231
Position Surface form Disambiguated ID Type / Status
Subject Belfry of Sint-Truiden E525009 entity
Predicate locatedIn P40 FINISHED
Object Sint-Truiden 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: Sint-Truiden | Statement: [Belfry of Sint-Truiden, locatedIn, Sint-Truiden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sint-Truiden
Context triple: [Belfry of Sint-Truiden, locatedIn, Sint-Truiden]
  • A. St. Truiden chosen
    St. Truiden is a historic Belgian city in the Limburg region, known for its medieval architecture and fruit-growing countryside.
  • B. Zottegem
    Zottegem is a city and municipality in East Flanders, Belgium, known for its historic center and its role as a regular feature in Flemish cycling races.
  • C. Mouscron
    Mouscron is a Belgian city in the province of Hainaut, near the French border in the region of Wallonia.
  • D. 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.
  • E. 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.
  • 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_69e7385b1c548190b940ded0163ee3ca completed April 21, 2026, 8:42 a.m.
Created at: April 16, 2026, 4:05 p.m.