Triple
T31440834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stickies |
E802060
|
entity |
| Predicate | saveBehavior |
P105400
|
FINISHED |
| Object | automatic saving of notes |
—
|
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: automatic saving of notes | Statement: [Stickies, saveBehavior, automatic saving of notes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: saveBehavior Context triple: [Stickies, saveBehavior, automatic saving of notes]
-
A.
saveBy
Indicates that one entity preserves, rescues, or protects another entity from loss, harm, or danger.
-
B.
archiveBehavior
chosen
Indicates the action or policy of storing items in an archive for long-term retention or reference.
-
C.
save
Indicates preserving or storing something from loss, harm, or use, often for future benefit or protection.
-
D.
savedBecauseOf
Indicates that one entity was preserved, rescued, or kept from loss specifically as a result of another entity’s action, presence, or influence.
-
E.
savedWhile
Indicates that one entity was saved or preserved during the time another event or action was occurring.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:05 p.m.