Triple

T22512770
Position Surface form Disambiguated ID Type / Status
Subject Seven Labors E556561 entity
Predicate hasPurposeInStory P80898 FINISHED
Object to prove Esfandiyar’s worthiness for kingship 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: to prove Esfandiyar’s worthiness for kingship | Statement: [Seven Labors, hasPurposeInStory, to prove Esfandiyar’s worthiness for kingship]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPurposeInStory
Context triple: [Seven Labors, hasPurposeInStory, to prove Esfandiyar’s worthiness for kingship]
  • A. hasDramaticPurpose
    Indicates that something serves a specific dramatic function or role within a narrative or performance.
  • B. narrativePurpose chosen
    Indicates the role or function that something serves within the structure or progression of a narrative.
  • C. hasPartInNarrative
    Indicates that one entity plays a role or participates as a component within the storyline or structure of another narrative entity.
  • D. hasThemeInStory
    Indicates that a particular theme is present or plays a significant role within a given story.
  • E. designedPurposeInFiction
    Indicates that something is intentionally created within a fictional context to serve a particular role, function, or narrative purpose.
  • 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_69e11e555edc81909ca803587dafd747 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15d61a27881909faed490d2b65f39 completed April 29, 2026, 1:22 a.m.
PD Predicate disambiguation batch_69ee625e3b408190a60c759fb0b28fe2 completed April 26, 2026, 7:07 p.m.
Created at: April 16, 2026, 8:50 p.m.