Triple

T15804261
Position Surface form Disambiguated ID Type / Status
Subject Ashkenazi tradition E383170 entity
Predicate includesFolklore P120146 FINISHED
Object Yiddish folktales 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: Yiddish folktales | Statement: [Ashkenazi tradition, includesFolklore, Yiddish folktales]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includesFolklore
Context triple: [Ashkenazi tradition, includesFolklore, Yiddish folktales]
  • A. folkloreFunction
    Indicates that something serves a role, purpose, or function within a body of folklore, such as myths, legends, or traditional narratives.
  • B. hasFolkTaleType
    Indicates that an entity (such as a story) is classified as belonging to a particular folk tale type or category.
  • C. hasRichOralTradition
    Indicates that an entity is associated with a longstanding, culturally significant body of stories, histories, or knowledge transmitted primarily through spoken word rather than written texts.
  • D. mythologicalCategory
    Indicates that one entity is classified as belonging to the mythological type, group, or category represented by the other entity.
  • E. basedOnOralTraditionsCollectedBy
    Indicates that something is derived from or informed by oral traditions that were gathered or recorded by a specified collector or source.
  • 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_69d86da2858c819090cc8481e7207b6e completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e0b525b1c08190acffab06d89dbdbe completed April 16, 2026, 10:08 a.m.
PD Predicate disambiguation batch_69e0053b847c8190945726c3ddac21cc completed April 15, 2026, 9:38 p.m.
PDg Predicate description generation batch_69e00e48d49c819081afccb02f9cf18b completed April 15, 2026, 10:16 p.m.
Created at: April 10, 2026, 4:48 a.m.