Triple
T35664985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rankoshi |
E1030537
|
entity |
| Predicate | hasSkiResortsNearby |
P1981
|
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: [Rankoshi, hasSkiResortsNearby, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkiResortsNearby Context triple: [Rankoshi, hasSkiResortsNearby, true]
-
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.
hasWinterSportsResort
Indicates that a location or entity possesses or hosts a resort specifically dedicated to winter sports activities.
-
C.
hasSkiResortType
Indicates that an entity is associated with, or classified by, a specific type or category of ski resort.
-
D.
hasSkiResortFeature
Indicates that a ski resort possesses or offers a specific feature, amenity, or characteristic.
-
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 (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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fab87b481908cd08697afe3bdd7 |
completed | May 3, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.