Triple
T33713264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ski Storsenter |
E863799
|
entity |
| Predicate | hasCustomerAmenity |
P194869
|
FINISHED |
| Object | restrooms |
—
|
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: restrooms | Statement: [Ski Storsenter, hasCustomerAmenity, restrooms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCustomerAmenity Context triple: [Ski Storsenter, hasCustomerAmenity, restrooms]
-
A.
hasPassengerAmenity
Indicates that an entity provides or is equipped with a specific amenity intended for the comfort or convenience of its passengers.
-
B.
hasAmenityAccessTo
Indicates that an entity has the right or ability to use or benefit from a specified amenity or facility.
-
C.
hasRegionalAmenity
Indicates that a region provides or contains a specific amenity or facility within its area.
-
D.
hasAccommodations
Indicates that one entity provides, contains, or offers lodging, facilities, or special arrangements for another entity.
-
E.
hasCustomerLounge
Indicates that an entity provides or includes a designated lounge area for customers to use.
- F. None of above. chosen
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_69f3498844608190bb8f9b14908d2510 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
| PDg | Predicate description generation | batch_69fd8ccaee848190acd59d7d643ad062 |
completed | May 8, 2026, 7:12 a.m. |
Created at: May 1, 2026, 1:43 a.m.