Triple

T2501081
Position Surface form Disambiguated ID Type / Status
Subject Bradford E52464 entity
Predicate twinTown P1072 FINISHED
Object Verviers E176726 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: Verviers | Statement: [Bradford, twinTown, Verviers]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Verviers
Context triple: [Bradford, twinTown, Verviers]
  • A. Verviers chosen
    Verviers is a city in eastern Belgium known historically for its textile industry and as a regional center in the province of Liège.
  • B. Binche
    Binche is a historic town in the Walloon region of Belgium, renowned for its well-preserved medieval architecture and its UNESCO-recognized Carnival of Binche.
  • C. Porrentruy
    Porrentruy is a historic town in northwestern Switzerland known for its medieval castle and role as a regional center in the canton of Jura.
  • D. Diekirch
    Diekirch is a town in northern Luxembourg known for its role in World War II, particularly during the country's liberation, and for its national military museum.
  • E. Bütgenbach
    Bütgenbach is a municipality in eastern Belgium’s German-speaking Community, known for its scenic lake, outdoor recreation, and proximity to the strategic Elsenborn Ridge.
  • 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_69ab4957b3a88190adf968ae0c1b931c completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd1b144a481909b1f8d96742a92e7 completed March 7, 2026, 7:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69b1eecac8548190941aa17044d11e59 completed March 11, 2026, 10:38 p.m.
Created at: March 6, 2026, 9:46 p.m.