Triple

T15187751
Position Surface form Disambiguated ID Type / Status
Subject Mayen-Koblenz E362920 entity
Predicate borders P224 FINISHED
Object Ahrweiler E939805 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: Ahrweiler | Statement: [Mayen-Koblenz, borders, Ahrweiler]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ahrweiler
Context triple: [Mayen-Koblenz, borders, Ahrweiler]
  • A. Ahrweiler chosen
    Ahrweiler is a district in the German state of Rhineland-Palatinate, known for its wine-growing Ahr Valley and historic towns.
  • B. Eschweiler
    Eschweiler is a town in western Germany near Aachen, known for its industrial history and location in the state of North Rhine-Westphalia.
  • 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. Wiehl
    Wiehl is a small town in western Germany’s North Rhine-Westphalia region, known for its picturesque setting in the hilly Bergisches Land and its mix of rural charm and light industry.
  • E. Neuß
    Neuß is an alternative spelling of Neuss, a historic city on the Rhine in North Rhine-Westphalia, Germany.
  • 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_69d85a09a39c81908759f23268e2d408 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0067995fc8190b048f15086bd42f0 completed April 15, 2026, 9:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69ff9976bc888190a050c2502d1f8e81 completed May 9, 2026, 8:30 p.m.
Created at: April 10, 2026, 3:09 a.m.