Triple
T26565449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VANOC |
E666367
|
entity |
| Predicate | hostedByResort |
P51015
|
FINISHED |
| Object | Whistler |
—
|
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: Whistler | Statement: [VANOC, hostedByResort, Whistler]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedByResort Context triple: [VANOC, hostedByResort, Whistler]
-
A.
isResortOf
Indicates that a location or facility functions as a resort associated with, belonging to, or serving a particular entity (such as a city, region, or organization).
-
B.
associatedResort
chosen
Indicates a relationship where one entity is linked or connected to a specific resort, typically as its related or corresponding resort.
-
C.
isResortDestinationFor
Indicates that a place serves as a resort destination specifically intended for or frequented by a particular person, group, or entity.
-
D.
hostedAttraction
Indicates that an entity served as the venue or location where a particular attraction, event, or feature was presented or took place.
-
E.
locatedInResortTown
Indicates that something is situated within the boundaries of a town that is primarily known as a resort or vacation destination.
- 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_69ee9cf7e94481909f0d556b36e43572 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f650c70d7c819093d9a0f005f7c8d5 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cab1f648190a2a9460690d18a37 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 1:55 a.m.