Triple
T35525495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grande Grotta climbing sector |
E1026660
|
entity |
| Predicate | climbingFeatures |
P184054
|
FINISHED |
| Object | tufa blobs |
—
|
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: tufa blobs | Statement: [Grande Grotta climbing sector, climbingFeatures, tufa blobs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingFeatures Context triple: [Grande Grotta climbing sector, climbingFeatures, tufa blobs]
-
A.
climbCharacteristic
Indicates a characteristic or property related to how an entity climbs or performs climbing actions.
-
B.
climbedFeatureType
Indicates that an entity has climbed or ascended a particular type of physical feature (such as a mountain, wall, or similar structure).
-
C.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
D.
climbingUse
Indicates that an entity uses or employs another entity as equipment, support, or aid specifically for climbing activities.
-
E.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
- F. None of above. chosen
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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: May 3, 2026, 4:04 p.m.