Triple
T30062714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Aino |
E763937
|
entity |
| Predicate | standardClimbingRouteFrom |
P92303
|
FINISHED |
| Object | Hirogawara |
—
|
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: Hirogawara | Statement: [Mount Aino, standardClimbingRouteFrom, Hirogawara]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardClimbingRouteFrom Context triple: [Mount Aino, standardClimbingRouteFrom, Hirogawara]
-
A.
standardClimbingRouteType
Indicates the classification of a climbing route according to a recognized grading or style system.
-
B.
climbingDifficultyStandardRoute
Indicates the level of difficulty associated with ascending via the standard or most commonly used route.
-
C.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
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.
isCleanClimbingRoute
Indicates that a climbing route can be ascended without using fixed or artificial protection for aid, relying only on natural features and removable gear.
- 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_69f2247221388190a13a22c47094a0ef |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 29, 2026, 6:58 p.m.