Triple
T2711440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stowe Mountain Resort |
E59869
|
entity |
| Predicate | isFourSeasonResort |
P42494
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Stowe Mountain Resort, isFourSeasonResort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFourSeasonResort Context triple: [Stowe Mountain Resort, isFourSeasonResort, true]
-
A.
isResortTown
Indicates that a town functions primarily as a resort destination, typically focused on tourism, leisure, and vacation activities.
-
B.
hasSkiLifts
Indicates that one location or facility is equipped with ski lifts that provide transportation for skiers or visitors.
-
C.
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.
-
D.
isSeasideResort
Indicates that a place functions as a resort located by the sea, typically offering coastal leisure and tourism activities.
-
E.
skiAreaType
Indicates the specific type or classification of a ski area associated with an entity (e.g., resort, backcountry, terrain park).
- 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_69ab4ac92a088190bc74bca14038e3de |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda78c4f08190bb1217f08198c4cc |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd8224c688190bb4a362360b03007 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8abcc348190bfa05c0abc4bcee7 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:55 p.m.