Triple
T21482343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clapis |
E530024
|
entity |
| Predicate | climbingCommunity |
P144530
|
FINISHED |
| Object | local French climbers |
—
|
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: local French climbers | Statement: [Clapis, climbingCommunity, local French climbers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingCommunity Context triple: [Clapis, climbingCommunity, local French climbers]
-
A.
coClimber
Indicates that two or more entities participate together in the same climbing activity or ascent.
-
B.
climbingCategory
Indicates the classification level or difficulty grade assigned to a climbing route, problem, or activity.
-
C.
climbingHabit
Indicates a relationship where an entity has a tendency or behavior of climbing, such as regularly ascending surfaces, structures, or other objects.
-
D.
climbingDiscipline
Indicates the specific style or category of climbing practiced or associated with an entity (e.g., bouldering, sport, trad).
-
E.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea34c4388190adc78d209d2aafb8 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631ec1d048190b6da97da8222e413 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:21 p.m.