Triple
T11655379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQL Mail |
E277000
|
entity |
| Predicate | alternative |
P4680
|
FINISHED |
| Object | Database Mail using SMTP |
—
|
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: Database Mail using SMTP | Statement: [SQL Mail, alternative, Database Mail using SMTP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternative Context triple: [SQL Mail, alternative, Database Mail using SMTP]
-
A.
ally
Indicates a cooperative relationship in which one entity supports, assists, or aligns with another, often for mutual benefit or a shared goal.
-
B.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
-
C.
alternateDescription
Indicates that an entity has an additional or substitute textual description that can be used in place of its primary description.
-
D.
opposite
Indicates that one entity is positioned or oriented directly across from, or in a contrary or reverse relation to, another entity.
-
E.
variant
chosen
Indicates that one entity is an alternative form, version, or variation of another entity.
- 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.