Triple
T20598197
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Buller ski resort |
E506104
|
entity |
| Predicate | hasAccommodationTypes |
P17960
|
FINISHED |
| Object | hotels |
—
|
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: hotels | Statement: [Mount Buller ski resort, hasAccommodationTypes, hotels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccommodationTypes Context triple: [Mount Buller ski resort, hasAccommodationTypes, hotels]
-
A.
hasAccommodation
chosen
Indicates that an entity provides, owns, or is associated with a place for someone to stay or live.
-
B.
hasHotelType
Indicates that a hotel is classified as belonging to a specific type or category (e.g., resort, boutique, hostel).
-
C.
hasLodgeType
Indicates that an entity is associated with or classified by a particular type or category of lodge.
-
D.
hasAccommodationAtEndpoints
Indicates that the endpoints of something (e.g., a route, connection, or segment) each have available accommodation facilities.
-
E.
hasResortType
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).
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1e251c8190926dafe1402eb63c |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.