Triple
T37411646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beauty and the Beast (traditional fairy tale) |
E929586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | European folk narrative |
C29101
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: European folk narrative Context triple: [Beauty and the Beast (traditional fairy tale), instanceOf, European folk narrative]
-
A.
European legend
A European legend is a traditional narrative rooted in the history, folklore, and cultural imagination of European peoples, often blending real events or places with mythical, supernatural, or moral elements.
-
B.
folklore subject
A folklore subject is a recurring character, motif, or theme that appears in traditional stories, beliefs, and customs of a culture, reflecting its values, fears, and collective imagination.
-
C.
figure in Germanic heroic legend
A figure in Germanic heroic legend is a semi-historical or mythic individual—often a warrior, ruler, or tragic hero—whose deeds, lineage, and fate are celebrated in early Germanic poetry and saga tradition.
-
D.
legendary narrative
chosen
A legendary narrative is a traditional story, often rooted in historical events or figures, that has been embellished over time with mythical or supernatural elements to convey cultural values or explain the extraordinary.
-
E.
characters in English folklore
Characters in English folklore are the legendary figures, both human and supernatural, that populate traditional English tales, myths, and ballads, embodying cultural values, fears, and imaginations passed down through generations.
- F. None of above.
Provenance (1 batch)
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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.