Triple
T2555715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Database Mail |
E56725
|
entity |
| Predicate | hasStoredProcedure |
P15181
|
FINISHED |
| Object | sp_send_dbmail |
—
|
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: sp_send_dbmail | Statement: [Database Mail, hasStoredProcedure, sp_send_dbmail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStoredProcedure Context triple: [Database Mail, hasStoredProcedure, sp_send_dbmail]
-
A.
hasSpecialProcedure
chosen
Indicates that a particular entity is associated with or governed by a designated special procedure or process.
-
B.
hasProgramCode
Indicates that an entity is associated with a specific program identifier or code used to reference or classify it within a system.
-
C.
hasProcess
Indicates that an entity is associated with, participates in, or is characterized by a particular process.
-
D.
hasDatabase
Indicates that an entity possesses, uses, or is associated with a specific database.
-
E.
usedProceduralLanguage
Indicates that an entity carried out an action or implemented something by means of a procedural programming language.
- 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_69ab4a4bfec081908039988ec4c86e28 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd5a33234819082ad49fa6594b6be |
completed | March 7, 2026, 7:37 a.m. |
| PD | Predicate disambiguation | batch_69abd0c8b6f08190a68645db3e8b779a |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:48 p.m.