Triple
T34014287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riesengebirge |
E872196
|
entity |
| Predicate | hasLegendaryFigure |
P74718
|
FINISHED |
| Object | Rübezahl |
—
|
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: Rübezahl | Statement: [Riesengebirge, hasLegendaryFigure, Rübezahl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegendaryFigure Context triple: [Riesengebirge, hasLegendaryFigure, Rübezahl]
-
A.
associatedLegendaryFigure
chosen
Indicates that an entity is traditionally linked or connected to a particular legendary or mythological figure.
-
B.
famousLegend
Indicates that the subject is widely known and celebrated in stories, myths, or folklore, often with enduring cultural significance.
-
C.
hasLegendaryPlayer
Indicates that an entity (such as a team, club, or organization) is associated with at least one player recognized as legendary.
-
D.
hasMythicalFigure
Indicates that one entity is associated with, features, or includes a particular mythical or legendary figure.
-
E.
hasCultOrLegend
Indicates that an entity is associated with, or is the subject of, a cult, myth, or legendary tradition.
- 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_69f349a08848819084b348d64c1879c3 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fdbc5ef46c8190bbcfb9798f4615b7 |
completed | May 8, 2026, 10:35 a.m. |
| PD | Predicate disambiguation | batch_69fdbb270338819082ce3f73903e884f |
completed | May 8, 2026, 10:29 a.m. |
Created at: May 1, 2026, 1:51 a.m.