Triple

T34563774
Position Surface form Disambiguated ID Type / Status
Subject Maleva E887415 entity
Predicate culturalStereotypeElement P97370 FINISHED
Object mystical Romani seer 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: mystical Romani seer | Statement: [Maleva, culturalStereotypeElement, mystical Romani seer]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: culturalStereotypeElement
Context triple: [Maleva, culturalStereotypeElement, mystical Romani seer]
  • A. culturalStereotypeUsed
    Indicates that a cultural stereotype is being invoked, applied, or relied upon in the relationship or action between entities.
  • B. notableStereotype chosen
    Indicates that a commonly recognized stereotype is associated with the subject in relation to the object.
  • C. culturallyPerceivedAs
    Indicates that one entity is regarded or interpreted in a particular way by a culture or cultural group.
  • D. popularCultureTrait
    Indicates that an entity exhibits a characteristic, behavior, or element that is commonly recognized or influential within popular culture.
  • E. isCulturalStandardFor
    Indicates that something is recognized or accepted as the customary or normative practice, value, or behavior within a particular culture or cultural context.
  • 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_69f349d0c4d881908dd0950f5eb9ec0a completed April 30, 2026, 12:23 p.m.
NER Named-entity recognition batch_69fbad1e94988190b86d447a68e65067 completed May 6, 2026, 9:05 p.m.
PD Predicate disambiguation batch_69fba881b8e0819094790935152b99a1 completed May 6, 2026, 8:45 p.m.
Created at: May 1, 2026, 2:02 a.m.