Triple
T11655441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQL Server Agent |
E277001
|
entity |
| Predicate | canSendNotificationsVia |
P68428
|
FINISHED |
| Object |
—
|
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: email | Statement: [SQL Server Agent, canSendNotificationsVia, email]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSendNotificationsVia Context triple: [SQL Server Agent, canSendNotificationsVia, email]
-
A.
canSend
chosen
Indicates that one entity has the ability or permission to send something (such as a message, item, or data) to another entity.
-
B.
hasMessenger
Indicates that one entity uses or is associated with another entity as a messenger or intermediary for communication.
-
C.
communicationCapability
Indicates that one entity has the ability or means to communicate with another entity through some channel or modality.
-
D.
requiresNotification
Indicates that a particular action, event, or state must trigger a notification to be sent to relevant parties.
-
E.
canLiaiseWith
Indicates that one entity is able or permitted to communicate and coordinate directly with another entity for collaboration or information exchange.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3cee010819089cffdbefe5a6efb |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d85ddc780481909a3bc63832fe2bd2 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.