Triple

T36143458
Position Surface form Disambiguated ID Type / Status
Subject Froney Gibson E1045378 entity
Predicate employedByInFiction P34569 FINISHED
Object Compson family 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: Compson family | Statement: [Froney Gibson, employedByInFiction, Compson family]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: employedByInFiction
Context triple: [Froney Gibson, employedByInFiction, Compson family]
  • A. worksWithInFiction
    Indicates that two fictional characters are depicted as collaborating, interacting, or being associated with each other within a narrative work.
  • B. worksWithFictionalCharacter
    Indicates that one entity collaborates or interacts in a work-related context with another entity that is a fictional character.
  • C. officeAssumedInFiction
    Indicates that an entity is depicted as assuming or taking on an office or official position 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. fictionalOccupation chosen
    Indicates that one entity is the imaginary or narrative-based job, role, or profession attributed to another entity 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_69f76e37ace88190a906b107d388f5d1 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fbaebc8f2c8190b94f1b4a3ec92e8c completed May 6, 2026, 9:12 p.m.
PD Predicate disambiguation batch_69fbadf1e6008190a71bbd196ba06844 completed May 6, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:08 p.m.