Triple

T15670684
Position Surface form Disambiguated ID Type / Status
Subject Ardennes classics E377302 entity
Predicate notableClimb P6286 FINISHED
Object Cauberg E380672 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: Cauberg | Statement: [Ardennes classics, notableClimb, Cauberg]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Cauberg
Context triple: [Ardennes classics, notableClimb, Cauberg]
  • A. Cauberg chosen
    Cauberg is a famous short but steep hill in Valkenburg, the Netherlands, renowned as a decisive climb in professional road cycling races.
  • B. Nuweveldberge
    Nuweveldberge is a mountain range in South Africa that forms part of the Great Escarpment and is known for its rugged terrain and semi-arid Karoo landscapes.
  • C. Vaalserberg
    Vaalserberg is a hill in the southeastern Netherlands known as the country's highest point and the location of the tripoint where the borders of the Netherlands, Germany, and Belgium meet.
  • D. Diedenbergen
    Diedenbergen is a district of the town Hofheim am Taunus in the German state of Hesse.
  • E. Bergschenhoek
    Bergschenhoek is a town in the Dutch province of South Holland that serves as the administrative center of the municipality of Lansingerland.
  • 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_69d85cd2e28481909d4e975bee20872f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04f1254508190a77a16b7bfd299ad completed April 16, 2026, 2:53 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff67a431208190b7e0d1eefd55504a completed May 9, 2026, 4:58 p.m.
Created at: April 10, 2026, 4:16 a.m.