Triple

T30465821
Position Surface form Disambiguated ID Type / Status
Subject Peter Pattieson E775135 entity
Predicate hasMetaFictionalRole P12417 FINISHED
Object fictional collector of stories 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: fictional collector of stories | Statement: [Peter Pattieson, hasMetaFictionalRole, fictional collector of stories]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMetaFictionalRole
Context triple: [Peter Pattieson, hasMetaFictionalRole, fictional collector of stories]
  • A. hasMetafictionalRole chosen
    Indicates that an entity plays a role within a story that self-consciously comments on, references, or breaks the conventions of fiction itself.
  • B. hasFictionalRole
    Indicates that an entity plays or is assigned a specific role within a fictional work or narrative.
  • C. isFictionalCharacter
    Indicates that the subject is a character that exists only in fiction rather than in real life.
  • D. hasFictionalType
    Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
  • E. hasFictionalScope
    Indicates that something pertains to, applies within, or is limited to a fictional or imagined context rather than real-world scope.
  • 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_69f2249622a48190b1fae2e3e4ee958a completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69fd974d75e08190af46b1d608769f3b completed May 8, 2026, 7:57 a.m.
PD Predicate disambiguation batch_69fd94ff792c8190bedf4a639d3da809 completed May 8, 2026, 7:47 a.m.
Created at: April 29, 2026, 8:11 p.m.