Triple
T37163266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WidgetKit |
E920731
|
entity |
| Predicate | supportsWidgetFamily |
P83861
|
FINISHED |
| Object | systemSmall |
—
|
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: systemSmall | Statement: [WidgetKit, supportsWidgetFamily, systemSmall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsWidgetFamily Context triple: [WidgetKit, supportsWidgetFamily, systemSmall]
-
A.
supportsWidgetType
chosen
Indicates that one entity is capable of handling, operating with, or being compatible with a specified type of widget.
-
B.
supportsFormFactorFamily
Indicates that one entity is compatible with and can operate using a specified family of physical or design form factors.
-
C.
supportsModelFamily
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or use of a particular model family.
-
D.
supportsHomeScreenWidgets
Indicates that an entity provides or allows the use of widgets on a device’s home screen.
-
E.
supportsInteractiveWidgets
Indicates that an entity is capable of handling or enabling interactive widgets within its context or environment.
- 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_69f76ea0429081908c711b55599eac3c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.