Triple
T34930823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ragni di Lecco |
E1007427
|
entity |
| Predicate | typicalClimbingArea |
P9786
|
FINISHED |
| Object | Grigna massif |
E708900
|
NE 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: Grigna massif | Statement: [Ragni di Lecco, typicalClimbingArea, Grigna massif]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClimbingArea Context triple: [Ragni di Lecco, typicalClimbingArea, Grigna massif]
-
A.
climbingArea
chosen
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
-
B.
climbingAreaType
Indicates the specific kind or classification of a climbing area associated with an entity (e.g., bouldering area, sport crag, alpine wall).
-
C.
isOutdoorClimbingArea
Indicates that a location functions as an outdoor area specifically designated or used for climbing activities.
-
D.
regionOfMountaineeringActivity
Indicates the geographic area where the mountaineering activity takes place or is carried out.
-
E.
climbingAreaStatus
Indicates the current condition or accessibility state of a climbing area (e.g., open, closed, restricted).
- F. None of above.
Provenance (4 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_69f76dc3d83881909d5c3c14455cfa2c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37a8b973088190a47f84945b4b8586 |
completed | June 21, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.