Triple
T9644472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salt Lake City–Ogden ski region |
E233157
|
entity |
| Predicate | typicalOpening |
P27375
|
FINISHED |
| Object | late November |
—
|
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: late November | Statement: [Salt Lake City–Ogden ski region, typicalOpening, late November]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOpening Context triple: [Salt Lake City–Ogden ski region, typicalOpening, late November]
-
A.
typicalOpeningPattern
chosen
Indicates that there is a commonly occurring or characteristic initial configuration, sequence, or arrangement associated with the given context.
-
B.
openingPractice
Indicates the practice or rehearsal of opening moves, procedures, or initial actions in a given context.
-
C.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
D.
openingTheme
Indicates that one entity serves as the opening theme (such as a song or musical piece) for another entity, typically a show, series, or similar work.
-
E.
initialOpening
Indicates the first or earliest instance in which something is opened, begun, or made accessible.
- 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_69ca848a5a908190aad251f4137b0c3a |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9b7fd2308190803a196ecdc80d76 |
completed | April 1, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b0263081908cf6df3eb07d71b0 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:12 p.m.