Triple

T26297032
Position Surface form Disambiguated ID Type / Status
Subject Kobo Nia E661444 entity
Predicate supportsOverDriveIntegration P41602 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: [Kobo Nia, supportsOverDriveIntegration, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsOverDriveIntegration
Context triple: [Kobo Nia, supportsOverDriveIntegration, yes]
  • A. offersDigitalBorrowingThrough chosen
    Indicates that one entity provides access to borrow digital items or content via another entity or platform.
  • B. supportsPhysicalMedia
    Indicates that one entity provides the capability to use, read, or handle physical media formats (such as discs, tapes, or printed materials) associated with another entity.
  • C. usesDRM
    Indicates that one entity applies digital rights management (DRM) controls or technologies to another entity (such as content, software, or media).
  • D. supportsDigitalDownloads
    Indicates that one entity enables or allows the other entity to provide or access digital file downloads.
  • E. hasCirculationFeature
    Indicates that an entity possesses a specific feature related to movement or flow within a system, such as circulation paths, routes, or mechanisms.
  • 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_69ee812cd48c81908054068f545f0526 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69fdbc5ef46c8190bbcfb9798f4615b7 completed May 8, 2026, 10:35 a.m.
PD Predicate disambiguation batch_69fdbb270338819082ce3f73903e884f completed May 8, 2026, 10:29 a.m.
Created at: April 26, 2026, 10:13 p.m.