Triple
T26297053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobo Nia |
E661444
|
entity |
| Predicate | supportsSideLoading |
P31926
|
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, supportsSideLoading, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSideLoading Context triple: [Kobo Nia, supportsSideLoading, yes]
-
A.
supportsThirdPartyApplications
chosen
Indicates that an entity is capable of working with, integrating, or allowing the use of software applications developed by external third parties.
-
B.
supportsDeviceManagement
Indicates that one entity provides capabilities or functionality to manage, configure, or control another entity’s devices.
-
C.
supportsInstallation
Indicates that one entity is capable of enabling, handling, or being compatible with the installation of another entity.
-
D.
supportsDebuggingTools
Indicates that an entity provides or is compatible with tools used for debugging or diagnosing issues.
-
E.
supportsProvisioningMethod
Indicates that one entity is capable of using or is compatible with a particular provisioning method offered or required by 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_69fe066d62b48190867df334039be786 |
completed | May 8, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69fe03afde3c8190a5b9b0778d19eb1a |
completed | May 8, 2026, 3:39 p.m. |
Created at: April 26, 2026, 10:13 p.m.