Triple
T26297042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobo Nia |
E661444
|
entity |
| Predicate | supportsReadingStats |
P3976
|
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, supportsReadingStats, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReadingStats Context triple: [Kobo Nia, supportsReadingStats, yes]
-
A.
containsReading
Indicates that one entity includes or encompasses a particular reading (such as a measurement, value, or interpretation) within it.
-
B.
usesReading
Indicates that one entity employs or relies on a particular reading (e.g., a text, measurement, or interpretation) in performing an action or fulfilling a function.
-
C.
hasStatistics
chosen
Indicates that an entity is associated with one or more statistical measures, records, or summaries describing its quantitative properties or performance.
-
D.
canBeReadWith
Indicates that one entity is suitable or compatible to be read or interpreted together with another entity.
-
E.
canRead
Indicates that one entity has the ability or permission to read or access the content of another entity.
- 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_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
Created at: April 26, 2026, 10:13 p.m.