Triple
T21802398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4632 |
E538268
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2783
RFC 2783 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
|
E1525423
|
NE FINISHED |
How this triple was built (4 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 2783 | Statement: [RFC 4632, obsoletes, RFC 2783]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2783 Context triple: [RFC 4632, obsoletes, RFC 2783]
-
A.
RFC 2763
RFC 2763 is an Internet Engineering Task Force (IETF) document that originally specified guidelines for classless inter-domain routing (CIDR) address allocation and aggregation before being superseded by RFC 4632.
-
B.
RFC 2782
RFC 2782 is an Internet standards document that originally specified the DNS SRV (Service) resource record for locating services in a domain.
-
C.
RFC 2773
RFC 2773 is an older Internet Engineering Task Force (IETF) document that specified an earlier approach to IP addressing and routing, later superseded by RFC 4632.
-
D.
RFC 2781
RFC 2781 is an Internet standards document that originally specified the transmission of Unicode (UTF-16) over networks before being superseded by later updates.
-
E.
RFC 2813
RFC 2813 is an Internet standards document that specifies the server-to-server protocol for the Internet Relay Chat (IRC) network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 2783 Triple: [RFC 4632, obsoletes, RFC 2783]
Generated description
RFC 2783 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2783 Target entity description: RFC 2783 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
-
A.
RFC 2763
RFC 2763 is an Internet Engineering Task Force (IETF) document that originally specified guidelines for classless inter-domain routing (CIDR) address allocation and aggregation before being superseded by RFC 4632.
-
B.
RFC 2782
RFC 2782 is an Internet standards document that originally specified the DNS SRV (Service) resource record for locating services in a domain.
-
C.
RFC 2773
RFC 2773 is an older Internet Engineering Task Force (IETF) document that specified an earlier approach to IP addressing and routing, later superseded by RFC 4632.
-
D.
RFC 2781
RFC 2781 is an Internet standards document that originally specified the transmission of Unicode (UTF-16) over networks before being superseded by later updates.
-
E.
RFC 2813
RFC 2813 is an Internet standards document that specifies the server-to-server protocol for the Internet Relay Chat (IRC) network.
- F. None of above. chosen
Provenance (5 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_69e0c4733f4081909a86622e7e6d15d2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f0780062688190a6c3a2a0364f0f77 |
completed | April 28, 2026, 9:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0aae5592e88190ad803c4e17026863 |
completed | May 18, 2026, 6:14 a.m. |
| NEDg | Description generation | batch_6a0aaefd48d48190a87ccf0417d1b991 |
completed | May 18, 2026, 6:17 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0aafcd0e148190a5bf048d28fdbddc |
completed | May 18, 2026, 6:21 a.m. |
Created at: April 16, 2026, 6:53 p.m.