Triple
T26297043
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobo Nia |
E661444
|
entity |
| Predicate | supportsReadingProfiles |
P195854
|
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, supportsReadingProfiles, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReadingProfiles Context triple: [Kobo Nia, supportsReadingProfiles, yes]
-
A.
supportsDeviceProfiles
Indicates that one entity is capable of recognizing, handling, or operating with specified device configuration profiles.
-
B.
usesProfile
Indicates that one entity employs, operates under, or is associated with a particular profile in performing its actions or functions.
-
C.
supportsMultiuser
Indicates that the subject is capable of handling or enabling simultaneous use by multiple users.
-
D.
supportsColorProfile
Indicates that one entity is capable of recognizing, handling, or applying the specified color profile associated with another entity.
-
E.
hasProfile
Indicates that an entity is associated with or possesses a specific profile representation or account.
- 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_69fdec5ffe088190ac5505f26c6cff18 |
completed | May 8, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69fdeae15f1c81908fc63fbc1b028d2e |
completed | May 8, 2026, 1:53 p.m. |
| PDg | Predicate description generation | batch_69fdec5f0420819087c0230ad384c4ba |
completed | May 8, 2026, 1:59 p.m. |
Created at: April 26, 2026, 10:13 p.m.