Triple

T9481408
Position Surface form Disambiguated ID Type / Status
Subject Maubeuge E228647 entity
Predicate twinnedWith P1072 FINISHED
Object Heinsberg E690485 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: Heinsberg | Statement: [Maubeuge, twinnedWith, Heinsberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Heinsberg
Context triple: [Maubeuge, twinnedWith, Heinsberg]
  • A. Heinsberg chosen
    Heinsberg is a town in western Germany’s North Rhine-Westphalia near the Dutch border, known as the administrative center of the Heinsberg district.
  • B. Neunkirchen
    Neunkirchen is a town in southwestern Germany known as one of the major urban centers and former industrial hubs of the state of Saarland.
  • C. Andernach
    Andernach is a historic German town on the Rhine River in Rhineland-Palatinate, known for its medieval architecture and one of the world’s highest cold-water geysers.
  • D. Bitburg
    Bitburg is a town in western Germany’s Eifel region, best known internationally for its Bitburger brewery and its nearby World War II military cemetery.
  • E. Neuss
    Neuss is a city in western Germany, near Düsseldorf, known as an administrative and commercial center with historical roots dating back to Roman times.
  • 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_69ca84730a5081908de282651019bf2f completed March 30, 2026, 2:10 p.m.
NER Named-entity recognition batch_69cd8018645c8190823d82a93635b345 completed April 1, 2026, 8:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69d1820ba67881909955c4198c7289b1 completed April 4, 2026, 9:26 p.m.
Created at: March 30, 2026, 7:54 p.m.