Triple
T11888507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1730 |
E282852
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 3501 |
E39860
|
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: RFC 3501 | Statement: [RFC 1730, obsoletedBy, RFC 3501]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3501 Context triple: [RFC 1730, obsoletedBy, RFC 3501]
-
A.
RFC 3501
chosen
RFC 3501 is the Internet standard specification that defines version 4rev1 of the Internet Message Access Protocol (IMAP) used for accessing and managing email on a mail server.
-
B.
RFC 3821
RFC 3821 is an IETF standards document that specifies the Fibre Channel over TCP/IP (FCIP) protocol for transporting Fibre Channel frames over IP networks.
-
C.
RFC 3821
RFC 3821 is an Internet Engineering Task Force (IETF) standards document that specifies the Internet Fibre Channel Protocol (iFCP) for transporting Fibre Channel frames over IP networks.
-
D.
RFC 2821
RFC 2821 is an earlier Internet standard that defined the Simple Mail Transfer Protocol (SMTP) for email transmission before being superseded by RFC 5321.
-
E.
RFC 2822
RFC 2822 is an Internet standard that defines the format for text-based email messages, updating and replacing the earlier RFC 822 specification.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d3a2860c8190a21af5fcddbd2f1e |
completed | April 10, 2026, 10:40 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f417e919548190acbc248879f957ec |
completed | May 1, 2026, 3:03 a.m. |
Created at: April 8, 2026, 9:44 p.m.