Triple
T25773649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ben |
E649086
|
entity |
| Predicate | hasMainAscentRouteFrom |
P73321
|
FINISHED |
| Object | Rowardennan |
—
|
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: Rowardennan | Statement: [The Ben, hasMainAscentRouteFrom, Rowardennan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainAscentRouteFrom Context triple: [The Ben, hasMainAscentRouteFrom, Rowardennan]
-
A.
hasPopularAscentRouteFrom
chosen
Indicates that there exists a commonly used or well-known route for ascending to a place or peak starting from the specified origin location.
-
B.
hasClimbingRoutesOn
Indicates that one entity possesses or features climbing routes located on another entity (such as a rock face, wall, or structure).
-
C.
climbsTo
Indicates that one entity moves upward, typically with effort or by climbing, until it reaches another entity or a higher position.
-
D.
firstAscentRouteOf
Indicates that a particular climbing route is the one used for the first successful ascent of a specific peak or climbing objective.
-
E.
hasNumberOfClimbingRoutes
Indicates the quantity of climbing routes that are associated with or available at a given entity.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 22, 2026, 5:32 a.m.