Triple

T29161057
Position Surface form Disambiguated ID Type / Status
Subject The Physics of Star Trek E739187 entity
Predicate targetFranchiseFandom P139852 FINISHED
Object Star Trek fans 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: Star Trek fans | Statement: [The Physics of Star Trek, targetFranchiseFandom, Star Trek fans]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: targetFranchiseFandom
Context triple: [The Physics of Star Trek, targetFranchiseFandom, Star Trek fans]
  • A. favoriteFranchise
    Indicates that one entity is the preferred or most liked franchise of another entity.
  • B. fandomFranchise chosen
    Indicates that one entity is a fan community or fandom specifically devoted to the other entity as a franchise or media property.
  • C. gameFranchise
    Indicates that one entity is a video game franchise to which the other entity (such as a specific game, character, or related media) belongs or is associated.
  • D. intendedFranchise
    Indicates that one entity is planned or designated to become part of, or operate under, the franchise of another entity.
  • E. franchiseUniverse
    Indicates that multiple works, characters, or stories exist within and are connected by the same overarching fictional franchise or narrative universe.
  • 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_69f07cb528fc8190a556b73990c347c8 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69fba78aca4c8190b8f1831e8cc04e06 completed May 6, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69fba34a65a4819088bac6c17542d71c completed May 6, 2026, 8:23 p.m.
Created at: April 28, 2026, 11:48 a.m.