Triple

T35471836
Position Surface form Disambiguated ID Type / Status
Subject Vanguard Commander for Hunters E1025226 entity
Predicate fictionalRoleIn P48208 FINISHED
Object Destiny 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: Destiny universe | Statement: [Vanguard Commander for Hunters, fictionalRoleIn, Destiny universe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: fictionalRoleIn
Context triple: [Vanguard Commander for Hunters, fictionalRoleIn, Destiny universe]
  • A. fictionalCharacter
    Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
  • B. hasFictionalRole
    Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
  • C. appearsInFictionAs
    Indicates that one entity is depicted or represented as a character, figure, or element within a fictional work or narrative.
  • D. fictionalUniverseRole chosen
    Indicates the role or function an entity has within a particular fictional universe or narrative setting.
  • E. fictionalCharacterAssociatedWith
    Indicates that there is a notable connection or association between a fictional character and another entity, such as a work, creator, or 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_69f76dfadba0819083456aadcd6864ea completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ff1a972bf08190860696ffcd887c0f completed May 9, 2026, 11:29 a.m.
PD Predicate disambiguation batch_69ff184005d88190bf38283ebc499b28 completed May 9, 2026, 11:19 a.m.
Created at: May 3, 2026, 4:04 p.m.