Triple
T3845840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monte Zoncolan |
E93566
|
entity |
| Predicate | hasCyclingClimbCategory |
P39716
|
FINISHED |
| Object | hors catégorie |
—
|
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 | Statement: [Monte Zoncolan, hasCyclingClimbCategory, hors catégorie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCyclingClimbCategory Context triple: [Monte Zoncolan, hasCyclingClimbCategory, hors catégorie]
-
A.
hasClimbsCount
Indicates that an entity is associated with a specific number of climbs it has completed or is credited with.
-
B.
climbingClassification
Indicates the difficulty rating or grade assigned to a climbing route or problem.
-
C.
hasMountainSport
Indicates that an entity is associated with or offers a particular mountain-related sport or activity.
-
D.
climbingCategory
chosen
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
E.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb77a488190be7fc2a1211f1f2d |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:18 p.m.