Triple

T31031687
Position Surface form Disambiguated ID Type / Status
Subject Oceania series E790743 entity
Predicate hasFictionalWorldType P196544 FINISHED
Object secondary world 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: secondary world | Statement: [Oceania series, hasFictionalWorldType, secondary world]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasFictionalWorldType
Context triple: [Oceania series, hasFictionalWorldType, secondary world]
  • A. hasFictionalUniverseType
    Indicates that an entity is associated with, or belongs to, a particular type or category of fictional universe.
  • 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. hasFictionalUniverseStatus
    Indicates that an entity holds a particular status or classification within a fictional universe or continuity.
  • E. hasFictionalUniverseGenre
    Indicates that a fictional universe is associated with a particular genre that characterizes its overall style, themes, or narrative type.
  • F. None of above. chosen

Provenance (4 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_69f224c97a788190b5da1ead6038a74e completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69fe5c1a502081909d4024e514309c8e completed May 8, 2026, 9:56 p.m.
PD Predicate disambiguation batch_69fe5a9df21c819087153f5d0bcaa987 completed May 8, 2026, 9:50 p.m.
PDg Predicate description generation batch_69fe5c196f4081908f150d4cd6c528fa completed May 8, 2026, 9:56 p.m.
Created at: April 29, 2026, 8:59 p.m.