Triple
T18699942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petit Dru |
E457218
|
entity |
| Predicate | hasClimbingHistory |
P131733
|
FINISHED |
| Object | site of major rockfall events altering routes |
—
|
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: site of major rockfall events altering routes | Statement: [Petit Dru, hasClimbingHistory, site of major rockfall events altering routes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasClimbingHistory Context triple: [Petit Dru, hasClimbingHistory, site of major rockfall events altering routes]
-
A.
hasClimbingHistorySince
Indicates that an entity has been engaged in climbing activities continuously or recurrently starting from a specified point in time.
-
B.
hasClimbingActivity
chosen
Indicates that an entity engages in or is associated with a climbing-related activity.
-
C.
hasClimb
Indicates that an entity performs or is capable of performing a climbing action on or over another entity or surface.
-
D.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
-
E.
hasClimbingInterest
Indicates that an entity has an interest in or enthusiasm for climbing activities.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e562eb06b481908ef9efdb976008f3 |
completed | April 19, 2026, 11:19 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.