Triple
T3931876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blockhaus |
E90811
|
entity |
| Predicate | climbCategory |
P39716
|
FINISHED |
| Object | Hors catégorie (cycling) |
—
|
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 (cycling) | Statement: [Blockhaus, climbCategory, Hors catégorie (cycling)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbCategory Context triple: [Blockhaus, climbCategory, Hors catégorie (cycling)]
-
A.
climbingCategory
chosen
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
B.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
C.
climbingClass
Indicates the difficulty or grade level assigned to a climbing route, problem, or activity.
-
D.
climbingDiscipline
Indicates the specific style or category of climbing practiced or associated with an entity (e.g., bouldering, sport, trad).
-
E.
climbedFeatureType
Indicates that an entity has climbed or ascended a particular type of physical feature (such as a mountain, wall, or similar structure).
- 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_69aed95f26e0819094b0e71974543a19 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeeda98058819094dd6ab223670860 |
completed | March 9, 2026, 3:56 p.m. |
| PD | Predicate disambiguation | batch_69aee7625ad4819097e4e8a168c19274 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.