Triple

T26297046
Position Surface form Disambiguated ID Type / Status
Subject Kobo Nia E661444 entity
Predicate supportsLineSpacingAdjustment P195964 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, supportsLineSpacingAdjustment, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: supportsLineSpacingAdjustment
Context triple: [Kobo Nia, supportsLineSpacingAdjustment, yes]
  • A. supportsLine
    Indicates that one entity provides structural, functional, or conceptual backing or reinforcement to a particular line (such as a line of text, code, argument, or physical alignment).
  • B. hasAlternativeSpacing
    Indicates that an entity is associated with one or more alternative ways of spacing its characters or components compared to a primary or standard form.
  • C. hasLineation
    Indicates that one entity applies or exhibits a particular system or pattern of line division (lineation) in relation to another entity, such as a text, surface, or layout.
  • D. hasStopSpacing
    Indicates that there is a specified distance or interval between consecutive stops in a route or sequence.
  • E. supportsWordWrap
    Indicates that one entity provides or enables automatic wrapping of text onto the next line instead of extending it horizontally.
  • 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_69ee812cd48c81908054068f545f0526 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69fdfbafe32081909c62653ff4fc155c completed May 8, 2026, 3:05 p.m.
PD Predicate disambiguation batch_69fdf64db4a881908f8250e24ae3cefb completed May 8, 2026, 2:42 p.m.
PDg Predicate description generation batch_69fdfbae00e481908a2e4558b9dee07e completed May 8, 2026, 3:05 p.m.
Created at: April 26, 2026, 10:13 p.m.