Triple
T33376194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weston, Vermont |
E854633
|
entity |
| Predicate | hasNearbySkiAreas |
P1981
|
FINISHED |
| Object | Okemo Mountain Resort |
—
|
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: Okemo Mountain Resort | Statement: [Weston, Vermont, hasNearbySkiAreas, Okemo Mountain Resort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbySkiAreas Context triple: [Weston, Vermont, hasNearbySkiAreas, Okemo Mountain Resort]
-
A.
hasSkiResortNearby
chosen
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.
hasSkiAreaAccess
Indicates that an entity provides direct access to, or is directly connected with, a ski area or ski facilities.
-
C.
hasSkiAreaSide
Indicates that something is located on or associated with a particular side or slope of a ski area.
-
D.
hasSkiRunsFor
Indicates that something provides or includes ski runs that are suitable or intended for a particular user group or purpose.
-
E.
hasSkiCenter
Indicates that a location or entity possesses or hosts a ski center as one of its facilities or features.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:35 a.m.