Triple
T29727261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lachen |
E752215
|
entity |
| Predicate | hasOfficialWebsiteOfParent |
P175671
|
FINISHED |
| Object | https://www.diessen.de/ |
—
|
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: https://www.diessen.de/ | Statement: [Lachen, hasOfficialWebsiteOfParent, https://www.diessen.de/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialWebsiteOfParent Context triple: [Lachen, hasOfficialWebsiteOfParent, https://www.diessen.de/]
-
A.
hasOfficialWebsiteThrough
Indicates that an entity has an official website that is accessed, provided, or mediated via a specified intermediary, platform, or channel.
-
B.
hasPublisherWebsite
Indicates that an entity is associated with the official website of its publisher.
-
C.
hasArtistOfficialWebsite
Indicates that an artist is associated with a specific official website that represents them.
-
D.
hasCorporateWebsiteOfUnderlyingCompany
Indicates that an entity has a corporate website corresponding to the underlying company associated with it.
-
E.
hasBrandWebsite
Indicates that an entity has an associated official website representing its brand.
- F. None of above. chosen
Provenance (4 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_69f0d62a36a88190bf860f00da433ff8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: April 28, 2026, 7:40 p.m.