Triple

T3774671
Position Surface form Disambiguated ID Type / Status
Subject County of Loon E83279 entity
Predicate hasCity P316 FINISHED
Object Tongeren E238388 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: Tongeren | Statement: [County of Loon, hasCity, Tongeren]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Tongeren
Context triple: [County of Loon, hasCity, Tongeren]
  • A. Tongeren chosen
    Tongeren is a historic city in eastern Belgium, known as the country’s oldest town and for its well-preserved Roman and medieval heritage.
  • B. Betuwe
    Betuwe is a fertile riverine region in the Dutch province of Gelderland, renowned for its extensive fruit orchards and scenic landscapes between the Rhine and Waal rivers.
  • C. Uithoorn
    Uithoorn is a town and municipality in the province of North Holland in the Netherlands, situated along the Amstel River.
  • D. Nieuwenhoorn
    Nieuwenhoorn is a village in the western Netherlands that forms part of the province of South Holland.
  • E. Biezelinge
    Biezelinge is a small village in the Dutch province of Zeeland, known as the birthplace of former Prime Minister Jan Peter Balkenende.
  • 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_69b4e52ebd988190b6e3a7d8069b74be completed March 14, 2026, 4:33 a.m.
Created at: March 8, 2026, 3:36 p.m.