Triple
T9212221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colwyn Bay |
E221149
|
entity |
| Predicate | openedAsResortIn |
P30833
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Colwyn Bay, openedAsResortIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsResortIn Context triple: [Colwyn Bay, openedAsResortIn, 19th century]
-
A.
openedAsResort
chosen
Indicates that something began operating or was first established in the capacity of a resort.
-
B.
openedAsSkiArea
Indicates that an entity began operating or was first established specifically as a ski area.
-
C.
isResortOf
Indicates that a location or facility functions as a resort associated with, belonging to, or serving a particular entity (such as a city, region, or organization).
-
D.
skiResortOpeningSeason
Indicates the season or time of year during which a ski resort begins its operations and opens to visitors.
-
E.
resort
Indicates that one entity is used or turned to as a final or alternative option by another entity, often after other possibilities have been exhausted.
- 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_69ca83e9d0e081908bdb71097201a06c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccd9b69838819088f33ca995fce222 |
completed | April 1, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69cc660ce23c81909c7bbe10f4a05f36 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:27 p.m.