Triple
T16503631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low’s Peak |
E400863
|
entity |
| Predicate | summitPushUsuallyStartsAt |
P67356
|
FINISHED |
| Object | early morning |
—
|
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: early morning | Statement: [Low’s Peak, summitPushUsuallyStartsAt, early morning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitPushUsuallyStartsAt Context triple: [Low’s Peak, summitPushUsuallyStartsAt, early morning]
-
A.
typicalSummitPushStartTime
chosen
Indicates the usual time at which climbers begin their final ascent to a summit.
-
B.
summitDayFrom
Indicates the specific day on which a summit or peak event occurs relative to a given timeframe or schedule.
-
C.
summitAccessibleFrom
Indicates that a summit can be reached or accessed starting from a specified location or route.
-
D.
summitCount
Indicates the number of summits or peak ascents associated with an entity.
-
E.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e5100e48190a623d6ee2fefb87e |
completed | April 18, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.