Triple
T3451389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Google Calendar sidebar widget |
E72800
|
entity |
| Predicate | userAction |
P9769
|
FINISHED |
| Object | add new task |
—
|
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: add new task | Statement: [Google Calendar sidebar widget, userAction, add new task]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userAction Context triple: [Google Calendar sidebar widget, userAction, add new task]
-
A.
user
Indicates a relationship where an entity actively operates, controls, or interacts with another entity, typically as the primary agent or consumer of its function.
-
B.
actsOn
chosen
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
C.
fromAct
Indicates that an entity originates from, is produced by, or results from a specified action or event.
-
D.
featuresAction
Indicates that one entity includes, presents, or showcases a particular action as a notable characteristic or component.
-
E.
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.
- 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_69ad85b12a908190a1d10a6b03b4f8ae |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adba7465248190947f9096e230e1c4 |
completed | March 8, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_69adae0255b48190a9069f7871c7a012 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:16 p.m.