Triple

T28218876
Position Surface form Disambiguated ID Type / Status
Subject The Sea of Fertility tetralogy E711394 entity
Predicate publisherInJapanese P128773 FINISHED
Object Shinchōsha 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: Shinchōsha | Statement: [The Sea of Fertility tetralogy, publisherInJapanese, Shinchōsha]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: publisherInJapanese
Context triple: [The Sea of Fertility tetralogy, publisherInJapanese, Shinchōsha]
  • A. publisherJapaneseEdition chosen
    Indicates that an entity serves as the publisher responsible for the Japanese edition of another work or resource.
  • B. publisherInUnitedStates
    Indicates that the publisher associated with an entity is located in, or operates from, the United States.
  • C. publisherType
    Indicates the classification or category of a publisher in relation to a published work or entity.
  • D. publisherOfPrintVersion
    Indicates that an entity serves as the publisher responsible for the printed (physical) version of another entity.
  • E. publisherOfWorkAppearingIn
    Indicates that an entity is the publisher responsible for issuing a work in which another specified work appears (e.g., as part of a collection, volume, or compilation).
  • 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_69efb51cb5288190818c1f63a266af11 completed April 27, 2026, 7:12 p.m.
NER Named-entity recognition batch_69fb6fdc7eb081908ab8475efb38c430 completed May 6, 2026, 4:44 p.m.
PD Predicate disambiguation batch_69fb5a986e588190b7a10892bd2ff44c completed May 6, 2026, 3:13 p.m.
Created at: April 27, 2026, 10:45 p.m.