Triple

T15968339
Position Surface form Disambiguated ID Type / Status
Subject Borgloon E387254 entity
Predicate borderedBy P224 FINISHED
Object Sint-Truiden E524620 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: Sint-Truiden | Statement: [Borgloon, borderedBy, Sint-Truiden]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sint-Truiden
Context triple: [Borgloon, borderedBy, 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 (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_69d86da94ccc819083d187f5dc6a123e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e157277e7881908d49f4874766b3b5 completed April 16, 2026, 9:39 p.m.
NED1 Entity disambiguation (via context triple) batch_6a00b274fa3481908b019036cd2ae627 completed May 10, 2026, 4:29 p.m.
Created at: April 10, 2026, 4:54 a.m.