Triple

T29469507
Position Surface form Disambiguated ID Type / Status
Subject Two in One E747471 entity
Predicate hasMetaFictionalElements P12417 FINISHED
Object yes 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: yes | Statement: [Two in One, hasMetaFictionalElements, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMetaFictionalElements
Context triple: [Two in One, hasMetaFictionalElements, yes]
  • A. hasFictionalContent
    Indicates that something contains or includes material that is imaginary, invented, or not intended to represent real events or facts.
  • B. hasFictionalScope
    Indicates that something pertains to, applies within, or is limited to a fictional or imagined context rather than real-world scope.
  • C. 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.
  • D. hasFictionalFrame
    Indicates that one entity is presented or interpreted within the context of a fictional narrative, scenario, or imaginative framework provided by another entity.
  • E. hasFictionalType
    Indicates that an entity is associated with or classified under a particular type or category that is fictional rather than real.
  • 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_69f0bd42cf308190bb01b20bc5b7c2d0 completed April 28, 2026, 1:59 p.m.
NER Named-entity recognition batch_69fd4d1854988190be093b103a681798 completed May 8, 2026, 2:40 a.m.
PD Predicate disambiguation batch_69fd4c8d1a188190897c24527337814a completed May 8, 2026, 2:38 a.m.
Created at: April 28, 2026, 3:56 p.m.