Triple

T17600685
Position Surface form Disambiguated ID Type / Status
Subject Col d’Aspin E428690 entity
Predicate tourDeFranceCategory P128179 FINISHED
Object Category 1 climb (often) LITERAL 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: Category 1 climb (often) | Statement: [Col d’Aspin, tourDeFranceCategory, Category 1 climb (often)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: tourDeFranceCategory
Context triple: [Col d’Aspin, tourDeFranceCategory, Category 1 climb (often)]
  • A. TourDeFranceOverallWins
    Indicates the number of times an entity has won the overall general classification of the Tour de France.
  • B. TourDeFranceWins
    Indicates the number of times an entity has won the Tour de France cycling race.
  • C. GrandTour
    Indicates a comprehensive, often extended journey or series of visits undertaken to explore multiple places, typically for cultural, educational, or experiential purposes.
  • D. TourDeFranceWin
    Indicates that an entity has won the Tour de France cycling race, typically as the overall general classification winner for a given edition.
  • E. bestTourDeFranceResult
    Indicates the highest (best) finishing position an entity has ever achieved in the Tour de France.
  • F. None of above. chosen

Provenance (4 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_69d889e1c6148190ba76241e74688f8b completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46c48dfc08190ba360e6082cffa87 completed April 19, 2026, 5:46 a.m.
PD Predicate disambiguation batch_69e3b4fff0348190b899a32da537eaca completed April 18, 2026, 4:44 p.m.
PDg Predicate description generation batch_69e3bbb50b448190a59dd4be33c76db7 completed April 18, 2026, 5:13 p.m.
Created at: April 10, 2026, 5:51 a.m.