Triple
T18117696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col du Soulor |
E433649
|
entity |
| Predicate | cyclingCategoryInTourDeFrance |
P128179
|
FINISHED |
| Object | Category 1 climb |
—
|
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 | Statement: [Col du Soulor, cyclingCategoryInTourDeFrance, Category 1 climb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cyclingCategoryInTourDeFrance Context triple: [Col du Soulor, cyclingCategoryInTourDeFrance, Category 1 climb]
-
A.
tourDeFranceCategory
chosen
Indicates that an entity is classified into a specific category or classification related to the Tour de France.
-
B.
cyclingCategory
Indicates the classification or type of cycling activity or discipline associated with an entity.
-
C.
roleInTourDeFrance
Indicates the specific capacity or function an entity has within the context of the Tour de France (e.g., rider, team, official, or support role).
-
D.
cyclingUse
Indicates that one entity uses or is used for cycling, such as engaging in or supporting bicycle-based transportation or activity.
-
E.
touringCycle
Indicates a cyclical sequence of tours or visits that repeatedly occur in a recurring pattern.
- F. None of above.
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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddd737708190863fba97cdc20d88 |
completed | April 19, 2026, 1:51 p.m. |
| PD | Predicate disambiguation | batch_69e43313ca788190baa224269e71de49 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:28 a.m.