Triple
T12287168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Refuge des Oulettes de Gaube |
E292858
|
entity |
| Predicate | climbingAccess |
P104061
|
FINISHED |
| Object | routes on Vignemale |
—
|
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: routes on Vignemale | Statement: [Refuge des Oulettes de Gaube, climbingAccess, routes on Vignemale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingAccess Context triple: [Refuge des Oulettes de Gaube, climbingAccess, routes on Vignemale]
-
A.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
-
B.
climbingAllowed
Indicates that an entity is permitted to climb onto or up another entity or surface.
-
C.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
D.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
-
E.
canBeClimbedIn
Indicates that one entity is suitable or possible to climb while being inside or within 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9261e1570819084bb4fdb44aa6aea |
completed | April 10, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69d91c4d9a9c8190aeb7beaf9792d8f0 |
completed | April 10, 2026, 3:50 p.m. |
| PDg | Predicate description generation | batch_69d9261b7f088190b69fe6961015fce3 |
completed | April 10, 2026, 4:32 p.m. |
Created at: April 8, 2026, 9:52 p.m.