Triple
T29623539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hogsback Camp |
E755065
|
entity |
| Predicate | climbingRouteServed |
P92303
|
FINISHED |
| Object | Coleman–Deming route |
—
|
NE NERFINISHED |
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: Coleman–Deming route | Statement: [Hogsback Camp, climbingRouteServed, Coleman–Deming route]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingRouteServed Context triple: [Hogsback Camp, climbingRouteServed, Coleman–Deming route]
-
A.
hasClimbingRoutesOn
Indicates that one entity possesses or features climbing routes located on another entity (such as a rock face, wall, or structure).
-
B.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
C.
hasNumberOfClimbingRoutes
Indicates the quantity of climbing routes that are associated with or available at a given entity.
-
D.
primaryClimbingRouteFor
chosen
Indicates that one climbing route is the main or most commonly used route for ascending a particular climbing objective or feature.
-
E.
climbingRoutesInclude
Indicates that a set or collection of climbing routes contains or encompasses a particular climbing route as one of its members.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66e26eda081908c514b28a814b250 |
completed | May 2, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:36 p.m.