Triple
T17737870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randogne |
E442770
|
entity |
| Predicate | hasResortFunction |
P38274
|
FINISHED |
| Object | ski resort area |
—
|
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: ski resort area | Statement: [Randogne, hasResortFunction, ski resort area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResortFunction Context triple: [Randogne, hasResortFunction, ski resort area]
-
A.
hasResortHotel
Indicates that one entity owns, includes, or is associated with a resort hotel as part of its facilities or offerings.
-
B.
hasResortType
chosen
Indicates that an entity (such as a resort or accommodation) is associated with a specific category or type of resort (e.g., beach resort, ski resort, spa resort).
-
C.
hasReserveFunction
Indicates that an entity serves as a backup or secondary option that can perform the same function if the primary one is unavailable or fails.
-
D.
hasResortBrand
Indicates that a resort is associated with, operated by, or marketed under a specific resort brand.
-
E.
hasResortCommunity
Indicates that one entity includes, contains, or is associated with a resort-style residential or vacation community.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e47aca27448190943c75e723ceefcc |
completed | April 19, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:09 a.m.