Triple

T9936235
Position Surface form Disambiguated ID Type / Status
Subject Captain Trips E192765 entity
Predicate hasFictionalClassification P58963 FINISHED
Object weaponized influenza strain 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: weaponized influenza strain | Statement: [Captain Trips, hasFictionalClassification, weaponized influenza strain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalClassification
Context triple: [Captain Trips, hasFictionalClassification, weaponized influenza strain]
  • A. hasFictionalForm
    Indicates that an entity has a counterpart or representation that exists within a fictional or imaginary context.
  • B. hasFictionalProductionType
    Indicates that an entity is associated with a specific type or category of fictional production (such as a genre, format, or style).
  • C. hasFictionalFunction
    Indicates that an entity serves a role, purpose, or function within a fictional context or narrative.
  • D. hasFictionalWork
    Indicates that one entity is the creator, owner, or source of a fictional work associated with another entity.
  • E. hasFictionalProperty chosen
    Indicates that an entity possesses a property, attribute, or characteristic that exists only in a fictional or imaginary 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_69ca82dd978c8190947124ab0d3315ac completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cdb5e3bfa88190a88f20f2687a2583 completed April 2, 2026, 12:18 a.m.
PD Predicate disambiguation batch_69cd1d9428cc81909b4b4938566d78a7 completed April 1, 2026, 1:28 p.m.
Created at: March 30, 2026, 8:44 p.m.