Triple
T21046061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South East Gully |
E518453
|
entity |
| Predicate | isOnCrag |
P142602
|
FINISHED |
| Object | Great End north-east face |
—
|
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: Great End north-east face | Statement: [South East Gully, isOnCrag, Great End north-east face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnCrag Context triple: [South East Gully, isOnCrag, Great End north-east face]
-
A.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
-
B.
hasClimbingActivity
Indicates that an entity engages in or is associated with a climbing-related activity.
-
C.
hasClimbingRoutesOn
Indicates that one entity possesses or features climbing routes located on another entity (such as a rock face, wall, or structure).
-
D.
hasClimbingConditions
Indicates that specific environmental or situational conditions suitable for climbing are present or associated with something.
-
E.
isClimbingRouteFeatureOn
Indicates that a specific climbing route feature is located on or part of a particular climbing route.
- 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_69e0b50438e08190917e2538bb8bc034 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fcf3cac081909915a440fbb5c084 |
completed | April 21, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf6728881908a2a43a5c8804a2a |
completed | April 20, 2026, 7:55 a.m. |
| PDg | Predicate description generation | batch_69e5e2df1a888190b5b478e76bdf7fdf |
completed | April 20, 2026, 8:25 a.m. |
Created at: April 16, 2026, 2:33 p.m.