Triple
T36975643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun International |
E914687
|
entity |
| Predicate | typeOfResorts |
P88110
|
FINISHED |
| Object | integrated resorts |
—
|
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: integrated resorts | Statement: [Sun International, typeOfResorts, integrated resorts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfResorts Context triple: [Sun International, typeOfResorts, integrated resorts]
-
A.
typeOfResortDeveloped
Indicates that a specific kind or category of resort has been developed in relation to a given entity or location.
-
B.
skiAreaType
Indicates the specific type or classification of a ski area associated with an entity (e.g., resort, backcountry, terrain park).
-
C.
hasSkiResortType
Indicates that an entity is associated with, or classified by, a specific type or category of ski resort.
-
D.
skiResortBase
Indicates that a location serves as the base area or primary starting point of a ski resort.
-
E.
includesResortType
chosen
Indicates that one entity contains or offers a specific type or category of resort as part of its overall composition or services.
- 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_69f76e8d13b4819089af24a47ce092fc |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a033d975d788190aafc4be10d6c5c1c |
completed | May 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_6a033cc2668481908cb696e57632a68f |
completed | May 12, 2026, 2:44 p.m. |
Created at: May 3, 2026, 4:14 p.m.