Triple

T25801831
Position Surface form Disambiguated ID Type / Status
Subject Star Trek: Imzadi E649852 entity
Predicate titleCharacterRelationship P92378 FINISHED
Object imzadi bond between Riker and Troi 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: imzadi bond between Riker and Troi | Statement: [Star Trek: Imzadi, titleCharacterRelationship, imzadi bond between Riker and Troi]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: titleCharacterRelationship
Context triple: [Star Trek: Imzadi, titleCharacterRelationship, imzadi bond between Riker and Troi]
  • A. titleCharacterRelation chosen
    Indicates the relationship between a work’s title and a specific character it references or centers on.
  • B. relationshipToCharacter
    Indicates the specific type of personal, social, or narrative connection that one entity has to a given character.
  • C. characterActorRelationship
    Indicates a relationship where an actor portrays or is associated with a specific character in a work.
  • D. portraysCharacterRelationship
    Indicates that one entity depicts or represents the relationship between characters in another entity.
  • E. relatedCharacter
    Indicates that one character has a specified relationship or association with another character.
  • 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_69e7ab34f8c8819099f6c4dabdabf129 completed April 21, 2026, 4:52 p.m.
NER Named-entity recognition batch_69f6b49436b0819094e21603054d05d4 completed May 3, 2026, 2:36 a.m.
PD Predicate disambiguation batch_69f6b3a5fd8481909433e923c5e24e55 completed May 3, 2026, 2:32 a.m.
Created at: April 22, 2026, 6:40 a.m.