Triple
T25379967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scald Law |
E631357
|
entity |
| Predicate | commonlyClimbedWith |
P167259
|
FINISHED |
| Object | Carnethy Hill |
—
|
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: Carnethy Hill | Statement: [Scald Law, commonlyClimbedWith, Carnethy Hill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyClimbedWith Context triple: [Scald Law, commonlyClimbedWith, Carnethy Hill]
-
A.
climbedWith
Indicates that one entity climbed together with another entity, sharing the ascent as a joint activity.
-
B.
climbedBy
Indicates that something is ascended or scaled by an agent or entity.
-
C.
usuallyClimbedAs
Indicates that an object, route, or feature is most commonly or traditionally ascended in a particular style, manner, or configuration.
-
D.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
E.
typeOfClimb
Indicates the specific style or category of climbing activity associated with a climb (e.g., bouldering, sport, trad).
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f66a6468ec8190a43ed6cd8c797f42 |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
| PDg | Predicate description generation | batch_69f6691da93081909deaf680614fc900 |
completed | May 2, 2026, 9:14 p.m. |
Created at: April 21, 2026, 1:46 p.m.