Triple
T33107307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wittdün auf Amrum |
E847221
|
entity |
| Predicate | foundedAsSeasideResort |
P47050
|
FINISHED |
| Object | late 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: late 19th century | Statement: [Wittdün auf Amrum, foundedAsSeasideResort, late 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsSeasideResort Context triple: [Wittdün auf Amrum, foundedAsSeasideResort, late 19th century]
-
A.
foundedAsResort
chosen
Indicates that a place or establishment was originally created or established specifically to function as a resort.
-
B.
isSeasideResort
Indicates that a place functions as a resort located by the sea, typically offering coastal leisure and tourism activities.
-
C.
developedAsResortDuring
Indicates that a place was developed or transformed into a resort during a specified time period.
-
D.
wasSpaTown
Indicates that a place historically functioned as a spa town, known for its therapeutic baths or mineral springs.
-
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_69f3495686508190b76bf20fa5e00bf7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe6e492bf8819080b25221d13445ea |
completed | May 8, 2026, 11:14 p.m. |
| PD | Predicate disambiguation | batch_69fe6dd33a6881908fe9bbbc184cab51 |
completed | May 8, 2026, 11:12 p.m. |
Created at: May 1, 2026, 1:26 a.m.