Triple
T21802400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4632 |
E538268
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2785
RFC 2785 is an older Internet Engineering Task Force (IETF) standards document related to IP addressing and routing that was later superseded by RFC 4632.
|
E1528660
|
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 2785 | Statement: [RFC 4632, obsoletes, RFC 2785]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2785 Context triple: [RFC 4632, obsoletes, RFC 2785]
-
A.
RFC 2765
RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
-
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 2778
RFC 2778 is an Internet standards-track document that defines a model for presence and instant messaging, laying foundational concepts later refined by subsequent protocols.
-
D.
RFC 2783
RFC 2783 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
-
E.
RFC 2845
RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
- 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 2785 Triple: [RFC 4632, obsoletes, RFC 2785]
Generated description
RFC 2785 is an older Internet Engineering Task Force (IETF) standards document related to IP addressing and routing that was later superseded by RFC 4632.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2785 Target entity description: RFC 2785 is an older Internet Engineering Task Force (IETF) standards document related to IP addressing and routing that was later superseded by RFC 4632.
-
A.
RFC 2765
RFC 2765 is an Internet Engineering Task Force (IETF) standard that originally specified a mechanism for translating between IPv4 and IPv6 network protocols, later superseded by RFC 6145.
-
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 2778
RFC 2778 is an Internet standards-track document that defines a model for presence and instant messaging, laying foundational concepts later refined by subsequent protocols.
-
D.
RFC 2783
RFC 2783 is an older Internet Engineering Task Force (IETF) standards document that was later superseded by RFC 4632.
-
E.
RFC 2845
RFC 2845 is the Internet standard that specifies the Transaction SIGnature (TSIG) mechanism for securing DNS transactions using shared secret keys and message authentication codes.
- 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_6a0abc8a45e08190b51d5e484b2634a1 |
completed | May 18, 2026, 7:15 a.m. |
| NEDg | Description generation | batch_6a0abdd2f3d0819083793794029106ed |
completed | May 18, 2026, 7:20 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0abf8a0e6c8190b3b2e96d663bd268 |
completed | May 18, 2026, 7:28 a.m. |
Created at: April 16, 2026, 6:53 p.m.