Triple

T15829279
Position Surface form Disambiguated ID Type / Status
Subject Salur Kazan’in Yedi Baslı Ejderhayı Öldürdüğü Boy E383825 entity
Predicate heroAction P101399 FINISHED
Object slaying of the seven-headed dragon 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: slaying of the seven-headed dragon | Statement: [Salur Kazan’in Yedi Baslı Ejderhayı Öldürdüğü Boy, heroAction, slaying of the seven-headed dragon]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heroAction
Context triple: [Salur Kazan’in Yedi Baslı Ejderhayı Öldürdüğü Boy, heroAction, slaying of the seven-headed dragon]
  • A. heroDepicted
    Indicates that one entity is portrayed or represented as a hero in relation to another entity.
  • B. protagonistAction chosen
    Indicates that the referenced entity performs the central or primary action associated with the main character in a narrative or scenario.
  • C. heroClass
    Indicates the character class or role that a hero belongs to within a given system or context.
  • D. nativeHero
    Indicates that an entity is regarded as a heroic figure originating from or strongly associated with a particular place or community.
  • E. heroPower
    Indicates that an entity possesses or is associated with a particular heroic power or special ability.
  • 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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e11e62aba8819090978801f4df73fe completed April 16, 2026, 5:37 p.m.
PD Predicate disambiguation batch_69e005418f588190824d91ff7974dada completed April 15, 2026, 9:38 p.m.
Created at: April 10, 2026, 4:49 a.m.