Triple
T26218886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curbar Edge climbing area |
E655708
|
entity |
| Predicate | hasBouldering |
P131733
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Curbar Edge climbing area, hasBouldering, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBouldering Context triple: [Curbar Edge climbing area, hasBouldering, yes]
-
A.
hasClimbingActivity
chosen
Indicates that an entity engages in or is associated with a climbing-related activity.
-
B.
hasIndoorClimbingWall
Indicates that a place or facility includes an indoor climbing wall as one of its features or amenities.
-
C.
hasClimbs
Indicates that one entity performs or is associated with climbing activity on another entity (such as a route, structure, or surface).
-
D.
hasClimbingRoutesOn
Indicates that one entity possesses or features climbing routes located on another entity (such as a rock face, wall, or structure).
-
E.
hasRockClimbingPotential
Indicates that an entity possesses suitable characteristics or conditions for successful or promising rock 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_69ee5b4a77e08190bfcb5f8ecdc55abd |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 26, 2026, 8:55 p.m.