Triple
T35483901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ballon d’Alsace |
E1025537
|
entity |
| Predicate | hasClimbCategoryInTourDeFrance |
P117050
|
FINISHED |
| Object | Category 1 |
—
|
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 | Statement: [Ballon d’Alsace, hasClimbCategoryInTourDeFrance, Category 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbCategoryInTourDeFrance Context triple: [Ballon d’Alsace, hasClimbCategoryInTourDeFrance, Category 1]
-
A.
tourDeFranceCategory
Indicates that an entity is classified into a specific category or classification related to the Tour de France.
-
B.
cyclingClimbCategory
chosen
Indicates the difficulty classification assigned to a cycling climb based on its steepness, length, and overall challenge.
-
C.
hasMountainClassification
Indicates a classification relationship where a mountain is assigned a specific type, category, or classification.
-
D.
hasClimbType
Indicates the specific style or category of climbing associated with a given climbing route or activity.
-
E.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
- 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_69f76dfbcdd881908c7b0b6bc502252b |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 3, 2026, 4:04 p.m.