Triple
T27371443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parkhurst Mountain |
E690331
|
entity |
| Predicate | closestMajorResort |
P42027
|
FINISHED |
| Object | Whistler Blackcomb |
—
|
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 Blackcomb | Statement: [Parkhurst Mountain, closestMajorResort, Whistler Blackcomb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestMajorResort Context triple: [Parkhurst Mountain, closestMajorResort, Whistler Blackcomb]
-
A.
nearbyResortSection
Indicates that one resort section is located close to another resort section in physical proximity.
-
B.
nearbyResortArea
chosen
Indicates that a resort area is located close to or within a short distance of a specified place or entity.
-
C.
nearestMajorTrailPass
Indicates the relationship where a given location is associated with the closest significant trail crossing or pass along a major trail network.
-
D.
nearestMajorAttraction
Indicates the closest significant point of interest or landmark relative to a given location.
-
E.
nearbySummit
Indicates that one summit is located close to another summit in geographic space.
- 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_69ef51ff826081909e42c8e2bfb97941 |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 12:19 p.m.