Triple
T34544507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Summit Central |
E886886
|
entity |
| Predicate | isPartOfSkiComplexWith |
P67535
|
FINISHED |
| Object | Summit West |
E886885
|
NE 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: Summit West | Statement: [Summit Central, isPartOfSkiComplexWith, Summit West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfSkiComplexWith Context triple: [Summit Central, isPartOfSkiComplexWith, Summit West]
-
A.
partOfSkiArea
chosen
Indicates that one entity is a component or subdivision within a larger ski area.
-
B.
hasSkiLiftConnectionTo
Indicates a relationship where one location is directly connected to another by a ski lift, allowing travel between them via that lift.
-
C.
hasSkiRunsFor
Indicates that something provides or includes ski runs that are suitable or intended for a particular user group or purpose.
-
D.
hasSkiLiftConnectionWith
Indicates a relationship where two locations or areas are directly connected by a ski lift that allows travel between them.
-
E.
hasSkiAreaAccess
Indicates that an entity provides direct access to, or is directly connected with, a ski area or ski facilities.
- F. None of above.
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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff65987ff88190b09be64f7c0e1da9 |
completed | May 9, 2026, 4:49 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3740fce7fc8190a5f6a6d85b568482 |
completed | June 21, 2026, 1:40 a.m. |
| PD | Predicate disambiguation | batch_69ff6525b0548190bef7a9f009e00bb8 |
completed | May 9, 2026, 4:47 p.m. |
Created at: May 1, 2026, 2:02 a.m.