Triple
T34544454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpental |
E886884
|
entity |
| Predicate | isPartOfSkiComplex |
P67535
|
FINISHED |
| Object | Summit at Snoqualmie ski areas |
—
|
NE NERFINISHED |
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: Summit at Snoqualmie ski areas | Statement: [Alpental, isPartOfSkiComplex, Summit at Snoqualmie ski areas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfSkiComplex Context triple: [Alpental, isPartOfSkiComplex, Summit at Snoqualmie ski areas]
-
A.
partOfSkiArea
chosen
Indicates that one entity is a component or subdivision within a larger ski area.
-
B.
partOfResortComplexWith
Indicates that one entity is a component or facility within the same resort complex as the other entity, forming part of a shared resort property.
-
C.
hasSkiCenter
Indicates that a location or entity possesses or hosts a ski center as one of its facilities or features.
-
D.
hasSkiAreaAccess
Indicates that an entity provides direct access to, or is directly connected with, a ski area or ski facilities.
-
E.
hasSkiResortType
Indicates that an entity is associated with, or classified by, a specific type or category of ski resort.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: May 1, 2026, 2:02 a.m.