Triple
T5562926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allalinhorn |
E145807
|
entity |
| Predicate | climbingGradeHohlaubgrat |
P19708
|
FINISHED |
| Object | AD |
—
|
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: AD | Statement: [Allalinhorn, climbingGradeHohlaubgrat, AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climbingGradeHohlaubgrat Context triple: [Allalinhorn, climbingGradeHohlaubgrat, AD]
-
A.
climbingGradeContext
Indicates the grading system or contextual scale used to express the difficulty rating of a climb.
-
B.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
-
C.
primaryClimbingDifficulty
Indicates the main level of challenge or technical difficulty associated with a climbing route or problem.
-
D.
climbingRoute
Indicates a relationship where a path or sequence of holds is designated for ascending a surface, typically in rock climbing or similar activities.
-
E.
climbingClass
chosen
Indicates the difficulty or grade level assigned to a climbing route, problem, or activity.
- 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_69c008fdae24819081aa002ad99cd966 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c0201ba0e88190acd5bfaa5973f2d8 |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.