Triple
T5655853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borgholm |
E124616
|
entity |
| Predicate | isSummerResort |
P10141
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Borgholm, isSummerResort, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSummerResort Context triple: [Borgholm, isSummerResort, true]
-
A.
isResortTown
Indicates that a town functions primarily as a resort destination, typically focused on tourism, leisure, and vacation activities.
-
B.
isSeasideResort
chosen
Indicates that a place functions as a resort located by the sea, typically offering coastal leisure and tourism activities.
-
C.
isResortCityOn
Indicates that a city, characterized as a resort destination, is located on or directly adjacent to a specified geographic feature (such as a coast, lake, or mountain range).
-
D.
isFourSeasonResort
Indicates that a resort operates and is available to guests throughout all four seasons of the year.
-
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_69c0082774a481909d7e63fb2aad56ac |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c0236d3f94819095111c41a323612d |
completed | March 22, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_69c021ba4ec481909db8cdbf0e907dd6 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:42 p.m.