Triple

T10019725
Position Surface form Disambiguated ID Type / Status
Subject Jakarta Mail E200582 entity
Predicate supportsProtocol P203 FINISHED
Object SMTP E5622 NE 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: SMTP | Statement: [Jakarta Mail, supportsProtocol, SMTP]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: SMTP
Context triple: [Jakarta Mail, supportsProtocol, SMTP]
  • A. SMTP chosen
    SMTP (Simple Mail Transfer Protocol) is a standard communication protocol used for sending and routing email messages across IP networks.
  • B. Mailer
    Mailer is a surname most notably associated with American novelist, journalist, and essayist Norman Mailer.
  • C. Mailer
    Mailer is Symfony’s email-sending component that provides a flexible, secure, and extensible way to create and deliver emails in PHP applications.
  • D. MAIL
    MAIL is the stock ticker symbol for Mail.ru Group, a major Russian internet and online services company.
  • E. MessageLabs
    MessageLabs was a pioneering cloud-based email and web security services provider known for its anti-spam and anti-virus solutions for businesses.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca831c45f08190ac1505cc15076608 completed March 30, 2026, 2:05 p.m.
NER Named-entity recognition batch_69cdcd4f3a988190892cc698109be8b8 completed April 2, 2026, 1:58 a.m.
NED1 Entity disambiguation (via context triple) batch_69d26aaa38188190aed8c18eccd8a79d completed April 5, 2026, 1:59 p.m.
Created at: March 30, 2026, 8:53 p.m.