Triple
T4229139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avalanche Gulch route |
E94533
|
entity |
| Predicate | requiresStartTime |
P55446
|
FINISHED |
| Object | pre-dawn start for safer snow conditions |
—
|
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: pre-dawn start for safer snow conditions | Statement: [Avalanche Gulch route, requiresStartTime, pre-dawn start for safer snow conditions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresStartTime Context triple: [Avalanche Gulch route, requiresStartTime, pre-dawn start for safer snow conditions]
-
A.
startsAt
Indicates that an event, process, or state begins at a specific time, location, or point in a sequence.
-
B.
hasTimeStart
Indicates that an event, process, or state begins at a specific point in time.
-
C.
startDate
Indicates the point in time when an event, state, or relationship begins.
-
D.
startTimeAsRepresentative
Indicates the time at which an entity begins serving or acting in a representative capacity.
-
E.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e61ccc081909b880baf1d6a0f24 |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e4ace648190acf911853d4fcf86 |
completed | March 12, 2026, 11:37 p.m. |
Created at: March 12, 2026, 11:05 p.m.