Triple
T1423385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Summits |
E30275
|
entity |
| Predicate | typicalClimbingStyle |
P9785
|
FINISHED |
| Object | expedition mountaineering |
—
|
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: expedition mountaineering | Statement: [Seven Summits, typicalClimbingStyle, expedition mountaineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClimbingStyle Context triple: [Seven Summits, typicalClimbingStyle, expedition mountaineering]
-
A.
climbingDiscipline
chosen
Indicates the specific style or category of climbing practiced or associated with an entity (e.g., bouldering, sport, trad).
-
B.
climbingClass
Indicates the difficulty or grade level assigned to a climbing route, problem, or activity.
-
C.
climbingArea
Indicates that one entity is a designated location or site used for climbing activities in relation to another entity.
-
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.
canClimb
Indicates that one entity has the ability or permission to climb another entity or surface.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c52e4ed881908d85e0cb9fe851ac |
completed | March 1, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69a4c4752abc8190a33b634c4d6fad28 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.