Triple
T576472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | At a Glance widget |
E13768
|
entity |
| Predicate | userInterfaceElementType |
P6678
|
FINISHED |
| Object | home screen widget |
—
|
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: home screen widget | Statement: [At a Glance widget, userInterfaceElementType, home screen widget]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userInterfaceElementType Context triple: [At a Glance widget, userInterfaceElementType, home screen widget]
-
A.
userInterface
Indicates a relationship where one entity serves as the interface or interaction layer through which a user engages with another system, service, or resource.
-
B.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
C.
typeOfControl
Indicates the specific manner or mechanism by which one entity exercises control or influence over another.
-
D.
componentType
chosen
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
E.
fieldType
Indicates the classification or category that defines the nature or kind of a given field within a structure or context.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b68cc808190b1ba45bdad78443d |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c692288190b88f30299516b5ba |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.