Triple
T13033102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Col de la Schlucht |
E326489
|
entity |
| Predicate | climbCategoryInTourDeFrance |
P39716
|
FINISHED |
| Object | Category 2 |
—
|
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 2 | Statement: [Col de la Schlucht, climbCategoryInTourDeFrance, Category 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbCategoryInTourDeFrance Context triple: [Col de la Schlucht, climbCategoryInTourDeFrance, Category 2]
-
A.
climbingClassification
Indicates the difficulty rating or grade assigned to a climbing route or problem.
-
B.
firstTourDeFranceAscent
Indicates that the subject is the first entity to have ascended the specified climb or route during a Tour de France.
-
C.
climbingCategory
chosen
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
D.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
-
E.
climbs
Indicates that an entity moves upward onto or up the surface of another entity, typically overcoming vertical or inclined distance.
- 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_69d8076cc45c81908123123f43e69266 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97efe72348190b52fb4068f5fb829 |
completed | April 10, 2026, 10:51 p.m. |
| PD | Predicate disambiguation | batch_69d97dc39a0881908119c62e31bf6182 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:54 p.m.