Triple
T26182274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benedikt Supersaxo |
E654716
|
entity |
| Predicate | mainRegionOfClimbing |
P136500
|
FINISHED |
| Object | Pennine Alps |
—
|
NE NERFINISHED |
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: Pennine Alps | Statement: [Benedikt Supersaxo, mainRegionOfClimbing, Pennine Alps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRegionOfClimbing Context triple: [Benedikt Supersaxo, mainRegionOfClimbing, Pennine Alps]
-
A.
regionOfMountaineeringActivity
chosen
Indicates the geographic area where the mountaineering activity takes place or is carried out.
-
B.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
-
C.
firstAscentRegion
Indicates the geographic region where the first successful ascent of something (typically a mountain or climbing route) took place.
-
D.
climbingAreaType
Indicates the specific kind or classification of a climbing area associated with an entity (e.g., bouldering area, sport crag, alpine wall).
-
E.
hasClimbingRoutesOn
Indicates that one entity possesses or features climbing routes located on another entity (such as a rock face, wall, or 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_69ee5b469bc081908fe486453fdad810 |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60c71dfb48190a3f0ab63ecadbdfa |
completed | May 2, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:40 p.m.