Triple
T15250951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elbsandsteingebirge |
E364515
|
entity |
| Predicate | rockClimbingStyle |
P100624
|
FINISHED |
| Object | traditionelles Klettern |
—
|
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: traditionelles Klettern | Statement: [Elbsandsteingebirge, rockClimbingStyle, traditionelles Klettern]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rockClimbingStyle Context triple: [Elbsandsteingebirge, rockClimbingStyle, traditionelles Klettern]
-
A.
climbingDiscipline
Indicates the specific style or category of climbing practiced or associated with an entity (e.g., bouldering, sport, trad).
-
B.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
C.
climbingRockType
Indicates that an entity is associated with or characterized by a particular type of rock used or encountered in climbing activities.
-
D.
climbingClass
Indicates the difficulty or grade level assigned to a climbing route, problem, or activity.
-
E.
typeOfClimb
chosen
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
- 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_69d85a0dde7481908fc64d1e82d5d20d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007f728648190b2c86e4528542b65 |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:13 a.m.