Triple

T16133401
Position Surface form Disambiguated ID Type / Status
Subject Horton family E391458 entity
Predicate hasStorylineType P121234 FINISHED
Object romantic drama 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: romantic drama | Statement: [Horton family, hasStorylineType, romantic drama]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasStorylineType
Context triple: [Horton family, hasStorylineType, romantic drama]
  • A. hasStaffTypeInStory
    Indicates that a story involves or is associated with a particular type or category of staff.
  • B. hasZoneStoryline
    Indicates that a zone or area is associated with a specific overarching storyline or narrative arc.
  • C. hasStoryPath
    Indicates that there exists a defined narrative route or sequence of events connecting one entity to another within a story or interactive experience.
  • D. hasProtagonistJourneyType
    Indicates that a narrative work features a main character whose overarching journey follows a specific type or pattern (e.g., hero’s journey, coming-of-age, tragedy).
  • E. storyboardedBy
    Indicates that a visual narrative work (such as a film, animation, or sequence) has its scenes or shots planned and illustrated by a specific storyboard artist or creator.
  • 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_69d87f1bb0988190b490d273dbf3fd03 completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e21a02e0048190b4e2c6ff434c2d7a completed April 17, 2026, 11:31 a.m.
PD Predicate disambiguation batch_69e182885bc08190822ae7e8a4b8ac1f completed April 17, 2026, 12:44 a.m.
PDg Predicate description generation batch_69e1835b64948190ae1d2a9d4cc64acf completed April 17, 2026, 12:48 a.m.
Created at: April 10, 2026, 5:01 a.m.