Triple
T6619201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col de l’Iseran |
E149631
|
entity |
| Predicate | cyclingCategory |
P71554
|
FINISHED |
| Object | hors catégorie climb in Tour de France |
—
|
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: hors catégorie climb in Tour de France | Statement: [Col de l’Iseran, cyclingCategory, hors catégorie climb in Tour de France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cyclingCategory Context triple: [Col de l’Iseran, cyclingCategory, hors catégorie climb in Tour de France]
-
A.
bicycleType
Indicates the specific kind or category of bicycle associated with an entity.
-
B.
cyclingReputation
Indicates a reputation or standing that an entity has earned specifically through its cycling-related activities or behavior.
-
C.
bicycleUse
Indicates that an entity makes use of a bicycle for transportation, activity, or other purposes.
-
D.
cyclingVenue
Indicates a location or facility where cycling activities, such as training, racing, or recreational riding, take place.
-
E.
importanceInCycling
Indicates the degree to which something is considered significant, influential, or central within the context of cycling.
- 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_69c687ed8a9c81908bb671717cb192ef |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6bdb76ec48190b59d576170970cc9 |
completed | March 27, 2026, 5:26 p.m. |
Created at: March 27, 2026, 1:58 p.m.