Triple

T34982312
Position Surface form Disambiguated ID Type / Status
Subject Federation–Cardassian border realignment E1008847 entity
Predicate fictional event P120967 FINISHED
Object Star Trek universe 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: Star Trek universe | Statement: [Federation–Cardassian border realignment, fictional event, Star Trek universe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fictional event
Context triple: [Federation–Cardassian border realignment, fictional event, Star Trek universe]
  • A. fictionalEventMarked
    Indicates that an event is identified or designated as fictional rather than real.
  • B. fictionalUniverseEvent chosen
    Indicates an event or occurrence that takes place within a specific fictional universe or narrative continuity.
  • C. fictionalActivity
    Indicates that an entity participates in, performs, or is associated with an activity that exists only in fiction or imaginative contexts.
  • D. fictionalOutcome
    Indicates that an event, action, or situation leads to a result that occurs only within a fictional, imagined, or non-real context.
  • E. hasFictionalEventType
    Indicates that something is associated with, characterized by, or classified under a particular type or category of fictional event.
  • 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_69f76dc844a48190881951fffb83d17e completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69fedec693b08190b0f8bfdb921e0766 completed May 9, 2026, 7:14 a.m.
PD Predicate disambiguation batch_69fede16c1d48190a20d8a9c5722c307 completed May 9, 2026, 7:11 a.m.
Created at: May 3, 2026, 4:01 p.m.