Triple

T3774669
Position Surface form Disambiguated ID Type / Status
Subject County of Loon E83279 entity
Predicate hasCity P316 FINISHED
Object Hasselt E165235 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: Hasselt | Statement: [County of Loon, hasCity, Hasselt]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hasselt
Context triple: [County of Loon, hasCity, Hasselt]
  • A. Hasselt
    Hasselt is a historic small city in the Dutch province of Overijssel, known for its medieval center and canals.
  • B. Hasselt chosen
    Hasselt is a city in northeastern Belgium that serves as the capital of the province of Limburg in the Flemish region.
  • C. 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.
  • D. Leuven
    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.
  • 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_69ad8b235e608190b5a2b1d1bfcef50b completed March 8, 2026, 2:43 p.m.
NER Named-entity recognition batch_69adcc594c50819099ab5ac1b82f61a6 completed March 8, 2026, 7:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69bf70bb52008190aaf547dff5f0d904 completed March 22, 2026, 4:31 a.m.
Created at: March 8, 2026, 3:36 p.m.