Triple
T31263883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagle Rock (Santa Monica Mountains) |
E797196
|
entity |
| Predicate | hasRockClimbing |
P131733
|
FINISHED |
| Object | informal bouldering |
—
|
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: informal bouldering | Statement: [Eagle Rock (Santa Monica Mountains), hasRockClimbing, informal bouldering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRockClimbing Context triple: [Eagle Rock (Santa Monica Mountains), hasRockClimbing, informal bouldering]
-
A.
hasClimbingActivity
chosen
Indicates that an entity engages in or is associated with a climbing-related activity.
-
B.
hasClimbingInterest
Indicates that an entity has an interest in or enthusiasm for climbing activities.
-
C.
hasRockClimbingPotential
Indicates that an entity possesses suitable characteristics or conditions for successful or promising rock climbing activities.
-
D.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
-
E.
climbingActivity
Indicates an activity where an entity ascends or scales a surface, structure, or natural formation, typically using physical effort and coordination.
- 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_69f224dd5fdc81908a4cd24917b67668 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 29, 2026, 9:12 p.m.