Triple

T29208965
Position Surface form Disambiguated ID Type / Status
Subject Valentine E740494 entity
Predicate appearsInShortFiction P120500 FINISHED
Object Majipoor Chronicles 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: Majipoor Chronicles | Statement: [Valentine, appearsInShortFiction, Majipoor Chronicles]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appearsInShortFiction
Context triple: [Valentine, appearsInShortFiction, Majipoor Chronicles]
  • A. appearsInShortStoryBy
    Indicates that one entity is a character, element, or subject that appears within a short story authored by another entity.
  • B. appearsInShort chosen
    Indicates that an entity appears or is featured in a short-form work, such as a short film, short episode, or brief media piece.
  • C. hasPlaceInFiction
    Indicates that a fictional work or element is associated with, set in, or takes place within a particular fictional location or setting.
  • D. showWithinFiction
    Indicates that one entity is depicted, referenced, or occurs as part of the fictional world or narrative context of another entity.
  • E. hasRelativeInFiction
    Indicates that one entity has a relative or family member who appears as a character within a fictional work associated with the other entity.
  • 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_69f07cb974108190b7e86ca489a6ebb6 completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f7688dd3d08190ad13d0e780570a1c completed May 3, 2026, 3:23 p.m.
PD Predicate disambiguation batch_69f767fcf2f881908bacc7bfc38e68a5 completed May 3, 2026, 3:21 p.m.
Created at: April 28, 2026, 12:10 p.m.