Triple
T9963171
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1094 |
E195616
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 1813 |
E197888
|
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 1813 | Statement: [RFC 1094, obsoletedBy, RFC 1813]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1813 Context triple: [RFC 1094, obsoletedBy, RFC 1813]
-
A.
RFC 1813
chosen
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
B.
RFC 2813
RFC 2813 is an Internet standards document that specifies the server-to-server protocol for the Internet Relay Chat (IRC) network.
-
C.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
D.
RFC 1013
RFC 1013 is an early Internet standards document that specified aspects of TCP/IP protocol behavior before being superseded by later, more comprehensive specifications.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb718cd588190a4aac48220deddec |
completed | April 2, 2026, 12:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d23d993404819089c9a71d03721e0b |
completed | April 5, 2026, 10:46 a.m. |
Created at: March 30, 2026, 8:47 p.m.