Triple
T28616676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FindText |
E724287
|
entity |
| Predicate | notifiesVia |
P148774
|
FINISHED |
| Object | WM_COMMAND messages |
—
|
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: WM_COMMAND messages | Statement: [FindText, notifiesVia, WM_COMMAND messages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notifiesVia Context triple: [FindText, notifiesVia, WM_COMMAND messages]
-
A.
notificationType
Indicates the specific category or kind of notification associated with an event or action.
-
B.
notification
Indicates that one entity sends or presents an alert or message to another entity to inform them of some event, change, or required action.
-
C.
providesAlertsTo
Indicates that one entity sends or delivers alerts or notifications to another entity.
-
D.
requiresNotification
Indicates that a particular action, event, or state must trigger a notification to be sent to relevant parties.
-
E.
transmitsVia
chosen
Indicates that something is conveyed, sent, or carried from one entity to another through a specified medium, channel, or mechanism.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f652a492108190b885b955ce147d3c |
completed | May 2, 2026, 7:38 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 4:32 a.m.