Triple

T27065335
Position Surface form Disambiguated ID Type / Status
Subject Chloe Bennet E685157 entity
Predicate characterAliasAssociatedWith P83029 FINISHED
Object Skye / Daisy Johnson / Quake 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: Skye / Daisy Johnson / Quake | Statement: [Chloe Bennet, characterAliasAssociatedWith, Skye / Daisy Johnson / Quake]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: characterAliasAssociatedWith
Context triple: [Chloe Bennet, characterAliasAssociatedWith, Skye / Daisy Johnson / Quake]
  • A. characterAlias
    Indicates that one character is known or referred to by an alternative name or alias.
  • B. associatedWithCharacterAlias
    Indicates that one entity is linked to or connected with an alternative name or alias used for a particular character.
  • C. hasFictionalAlterEgoOf
    Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
  • D. fictionalCharacterAssociatedWith
    Indicates that there is a notable connection or association between a fictional character and another entity, such as a work, creator, or universe.
  • E. hasFictionalAlias chosen
    Indicates that an entity is known by an alternative name or identity within a fictional context.
  • 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_69ef14835fcc81908bd737b4267ae528 completed April 27, 2026, 7:47 a.m.
NER Named-entity recognition batch_69f7516d5b4081908588a6feb541f355 completed May 3, 2026, 1:45 p.m.
PD Predicate disambiguation batch_69f74d40ebb081909daf60623e38f41d completed May 3, 2026, 1:27 p.m.
Created at: April 27, 2026, 8:24 a.m.