Triple
T25834729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Linz am Rhein |
E650763
|
entity |
| Predicate | hasTourismSlogan |
P25952
|
FINISHED |
| Object | Die bunte Stadt am Rhein |
—
|
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: Die bunte Stadt am Rhein | Statement: [Linz am Rhein, hasTourismSlogan, Die bunte Stadt am Rhein]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourismSlogan Context triple: [Linz am Rhein, hasTourismSlogan, Die bunte Stadt am Rhein]
-
A.
tourismSlogan
chosen
Indicates that a phrase is used as a promotional slogan to attract tourists to a place or destination.
-
B.
hasTourismRegionBrand
Indicates that an entity is associated with or belongs to a specific tourism region brand used for destination marketing or regional tourism identity.
-
C.
touristRegionNickname
Indicates that a tourist region is known by a particular informal or colloquial nickname.
-
D.
isMottoOf
Indicates that a phrase or expression serves as the official motto associated with a particular entity.
-
E.
hasTourismAuthority
Indicates that an entity holds official responsibility or power to manage, regulate, or oversee tourism-related activities for another entity or area.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 22, 2026, 7:41 a.m.