Triple
T8147146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbolt Peak |
E190240
|
entity |
| Predicate | summitBlockDifficulty |
P80955
|
FINISHED |
| Object | technical climbing required |
—
|
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: technical climbing required | Statement: [Thunderbolt Peak, summitBlockDifficulty, technical climbing required]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitBlockDifficulty Context triple: [Thunderbolt Peak, summitBlockDifficulty, technical climbing required]
-
A.
summitCount
Indicates the number of summits or peak ascents associated with an entity.
-
B.
hasSummitCountApprox
Indicates that an entity is associated with an approximate number of summits or peak ascents.
-
C.
summitDepth
Indicates the vertical distance from a summit’s highest point down to a specified reference level, such as a base or surrounding terrain.
-
D.
hasSummitWidth
Indicates that an entity (typically a mountain or peak) has a specified measurement for the width of its summit area.
-
E.
hasHigherSummit
Indicates that one entity’s summit is higher in elevation than another entity’s summit.
- 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_69ca82be7ba8819087de0147e9292c83 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb447d6b1881908ff3fa25af6b4e80 |
completed | March 31, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb39d20e78819092ea9e04357be008 |
completed | March 31, 2026, 3:04 a.m. |
Created at: March 30, 2026, 5:36 p.m.