Triple
T6992227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Disappointment Cleaver route |
E162110
|
entity |
| Predicate | standardStartTime |
P32533
|
FINISHED |
| Object | early morning alpine start |
—
|
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 alpine start | Statement: [Disappointment Cleaver route, standardStartTime, early morning alpine start]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardStartTime Context triple: [Disappointment Cleaver route, standardStartTime, early morning alpine start]
-
A.
standardTimeType
Indicates that a time value is expressed using a particular standard or conventional time format or classification.
-
B.
requiresStartTime
Indicates that an entity cannot be valid, initiated, or executed unless a specific start time has been provided or is in effect.
-
C.
standardTimeCounterpart
Indicates that one time representation is the corresponding value expressed in a standard or canonical time format for the other.
-
D.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
E.
typicalStartPeriod
chosen
Indicates the usual or standard time period during which something begins or is initiated.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbc1f63c8190837cfd71cf5ed613 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.