Triple

T30349753
Position Surface form Disambiguated ID Type / Status
Subject Ore no Kanojo to Osananajimi ga Shuraba Sugiru E771960 entity
Predicate lightNovelFirstPublicationYear P110890 FINISHED
Object 2011 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: 2011 | Statement: [Ore no Kanojo to Osananajimi ga Shuraba Sugiru, lightNovelFirstPublicationYear, 2011]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: lightNovelFirstPublicationYear
Context triple: [Ore no Kanojo to Osananajimi ga Shuraba Sugiru, lightNovelFirstPublicationYear, 2011]
  • A. lightNovelMainImprintRunEndYear
    Indicates the calendar year in which the main imprint’s publication run of the light novel ended.
  • B. novelReleaseYear chosen
    Indicates the calendar year in which a novel was first released or published.
  • C. lightNovelPublisherLabel
    Indicates that an entity serves as the publishing company responsible for releasing a particular light novel.
  • D. lightNovelPublisherCountry
    Indicates the country in which the publisher of a given light novel is based.
  • E. workOfFictionStartDate
    Indicates the date on which a work of fiction was first created, published, released, or otherwise began to exist as a distinct fictional work.
  • 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_69f2248b9a208190bc3e6804acd5afd6 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f69dfdda708190be290c7bec205445 completed May 3, 2026, 12:59 a.m.
PD Predicate disambiguation batch_69f69d1a37e081908d1d86b90ff502bd completed May 3, 2026, 12:55 a.m.
Created at: April 29, 2026, 7:56 p.m.