Triple
T13847090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travemünde |
E332834
|
entity |
| Predicate | isSeasideResortSince |
P10141
|
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: [Travemünde, isSeasideResortSince, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSeasideResortSince Context triple: [Travemünde, isSeasideResortSince, 19th century]
-
A.
isSeasideResort
chosen
Indicates that a place functions as a resort located by the sea, typically offering coastal leisure and tourism activities.
-
B.
isSeasideVillage
Indicates that a village is located directly by the sea or coastline.
-
C.
isResortTown
Indicates that a town functions primarily as a resort destination, typically focused on tourism, leisure, and vacation activities.
-
D.
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).
-
E.
isResortDestinationFor
Indicates that a place serves as a resort destination specifically intended for or frequented by a particular person, group, or entity.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02b2a9788190b164760adec64ef6 |
completed | April 14, 2026, 9:02 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.