Triple
T4731347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windham Mountain |
E105014
|
entity |
| Predicate | offersEquipmentRental |
P59087
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Windham Mountain, offersEquipmentRental, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersEquipmentRental Context triple: [Windham Mountain, offersEquipmentRental, yes]
-
A.
rentalModel
Indicates that one entity is used or provided to another under a specific rental arrangement, defining how the rental relationship is structured or operates.
-
B.
hasSunbedRental
Indicates that an entity offers or provides sunbed rental services to others.
-
C.
peakEquipment
Indicates that an entity is using or associated with the maximum or highest-capacity level of equipment available in a given context.
-
D.
usedEquipmentFrom
Indicates that one entity has utilized or operated equipment that originated from or was provided by another entity.
-
E.
availableFor
Indicates that one entity can be used, accessed, or allocated for the benefit, purpose, or use of another entity.
- 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_69bd43ee52048190b81a4f066534ffb3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd67c9c3c08190a6c4944cdd1362a8 |
completed | March 20, 2026, 3:29 p.m. |
| PD | Predicate disambiguation | batch_69bd6220071881909670c89d072ffb6d |
completed | March 20, 2026, 3:05 p.m. |
| PDg | Predicate description generation | batch_69bd67c895dc8190ba648002ff54424b |
completed | March 20, 2026, 3:29 p.m. |
Created at: March 20, 2026, 1:19 p.m.