Triple
T25466415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Küssnacht |
E638185
|
entity |
| Predicate | hasSiteRelatedToLegend |
P162100
|
FINISHED |
| Object | Hohle Gasse |
—
|
NE NERFINISHED |
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: Hohle Gasse | Statement: [Küssnacht, hasSiteRelatedToLegend, Hohle Gasse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiteRelatedToLegend Context triple: [Küssnacht, hasSiteRelatedToLegend, Hohle Gasse]
-
A.
hasLegendAssociatedWith
Indicates that something is connected to or accompanied by a traditional story, myth, or legend.
-
B.
hasSiblingInLegend
Indicates that one entity is described as the sibling of another entity within a mythological or legendary narrative.
-
C.
mentionsLegend
Indicates that one entity makes reference to or cites a legendary figure, story, or concept associated with another entity.
-
D.
containsSite
Indicates that one entity spatially or structurally includes another entity as a site or location within its bounds.
-
E.
hasHistoricalLegend
Indicates that there exists a traditional story, myth, or legend associated with the subject, typically rooted in historical or cultural narratives.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f622abdfac8190988421c946411d7e |
completed | May 2, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 21, 2026, 2:14 p.m.