Triple

T26311167
Position Surface form Disambiguated ID Type / Status
Subject Charles "Biffy" Biffen E661824 entity
Predicate inhabitsFictionalUniverse P79039 FINISHED
Object Jeeves and Wooster 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: Jeeves and Wooster universe | Statement: [Charles "Biffy" Biffen, inhabitsFictionalUniverse, Jeeves and Wooster universe]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: inhabitsFictionalUniverse
Context triple: [Charles "Biffy" Biffen, inhabitsFictionalUniverse, Jeeves and Wooster universe]
  • A. hasFictionalInhabitants
    Indicates that a place or setting is inhabited by fictional or imaginary beings.
  • B. hasFictionalUniverseProperty
    Indicates that a fictional universe possesses a specific characteristic, attribute, or property.
  • C. hasFictionalUniverseElement
    Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
  • D. activeInFictionalUniverse chosen
    Indicates that an entity participates, operates, or has a role within a specified fictional universe or setting.
  • E. hasFictionalUniverseType
    Indicates that an entity is associated with, or belongs to, a particular type or category of fictional 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_69ee812dacfc81908484aade9120fba9 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f60ee7e6348190951e6f9647f5555b completed May 2, 2026, 2:49 p.m.
PD Predicate disambiguation batch_69f602d2ec748190ae95154f34c7878f completed May 2, 2026, 1:57 p.m.
Created at: April 26, 2026, 10:22 p.m.