Triple
T1631413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 821 |
E35264
|
entity |
| Predicate | title |
P38
|
FINISHED |
| Object | Simple Mail Transfer Protocol |
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: Simple Mail Transfer Protocol | Statement: [RFC 821, title, Simple Mail Transfer Protocol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Simple Mail Transfer Protocol Context triple: [RFC 821, title, Simple Mail Transfer Protocol]
-
A.
SMTP
chosen
SMTP (Simple Mail Transfer Protocol) is a standard communication protocol used for sending and routing email messages across IP networks.
-
B.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
C.
POP3
POP3 (Post Office Protocol version 3) is a standard email protocol used by clients to retrieve messages from a remote mail server over a TCP/IP network, typically downloading them for local storage.
-
D.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
E.
Host-to-Host Protocol
Host-to-Host Protocol was an early ARPANET communication protocol that provided reliable end-to-end data transfer between computers, serving as a precursor to modern transport protocols like TCP.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a909f5ae98819091ce5e00eb4256a2 |
completed | March 5, 2026, 4:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad58d79bc88190bfc62f53dd8e8b90 |
completed | March 8, 2026, 11:09 a.m. |
Created at: March 4, 2026, 7:28 p.m.