Triple

T25225525
Position Surface form Disambiguated ID Type / Status
Subject Emissary (Star Trek: Deep Space Nine) E632076 entity
Predicate featuresFlashbackTo P169512 FINISHED
Object Battle of Wolf 359 NE NERFINISHED

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: Battle of Wolf 359 | Statement: [Emissary (Star Trek: Deep Space Nine), featuresFlashbackTo, Battle of Wolf 359]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: featuresFlashbackTo
Context triple: [Emissary (Star Trek: Deep Space Nine), featuresFlashbackTo, Battle of Wolf 359]
  • A. featuresFlashback chosen
    Indicates that an event, scene, or narrative segment includes a flashback to an earlier time or prior events.
  • B. featuresReturnOf
    Indicates that something (such as a work, event, or product) includes or highlights the comeback or reappearance of a person, character, element, or feature.
  • C. featuresReimaginedVersionOf
    Indicates that something includes or presents a newly interpreted or updated version of another existing work or element.
  • D. featuresHistorian
    Indicates that something includes or presents a historian as a notable participant, subject, or element.
  • E. flashbackStructure
    Indicates a narrative relationship where events are presented out of chronological order by returning to earlier moments in time (flashbacks) to inform or reframe the current storyline.
  • 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_69e75a8e0f688190a7aebe9a4815e25b completed April 21, 2026, 11:07 a.m.
NER Named-entity recognition batch_69f68f670b608190a0b6ab60d722b4e0 completed May 2, 2026, 11:57 p.m.
PD Predicate disambiguation batch_69f68b78f29481908cc8f390496dee97 completed May 2, 2026, 11:40 p.m.
Created at: April 21, 2026, 1:03 p.m.