Triple
T139093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Squaw Valley |
E2812
|
entity |
| Predicate | hasSkiLifts |
P5970
|
FINISHED |
| Object | chairlifts |
—
|
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: chairlifts | Statement: [Squaw Valley, hasSkiLifts, chairlifts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkiLifts Context triple: [Squaw Valley, hasSkiLifts, chairlifts]
-
A.
hasSkiResortNearby
Indicates that one location is situated close enough to another location that it can be considered to have a ski resort in its vicinity.
-
B.
hasGlacier
Indicates that one entity possesses, contains, or is characterized by the presence of a glacier.
-
C.
hasMountainRange
Indicates that one entity possesses, contains, or is geographically associated with a specific mountain range.
-
D.
hasMajorMountainRange
Indicates that one entity possesses, contains, or is geographically associated with a principal or significant mountain range.
-
E.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
- 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_69a2521e35c08190b28e5c9f1e3c9b59 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a800148190be119d1d075869b8 |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a2565426c08190aab68e34a6a2d60e |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a25737f9188190b9690dce98aed83a |
completed | Feb. 28, 2026, 2:47 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.