Triple
T23362874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4291 |
E593231
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 3513
RFC 3513 is an earlier Internet standard that defined the addressing architecture for IPv6 before being superseded by RFC 4291.
|
E1584709
|
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 3513 | Statement: [RFC 4291, obsoletes, RFC 3513]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3513 Context triple: [RFC 4291, obsoletes, RFC 3513]
-
A.
RFC 3653
RFC 3653 is an Internet Engineering Task Force (IETF) standards-track document that specifies aspects of the Message Session Relay Protocol (MSRP) used for transmitting instant messages and related media over IP networks.
-
B.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
C.
RFC 3413
RFC 3413 is an Internet standard that specifies the Simple Network Management Protocol (SNMPv3) applications, including notification, proxy, and command generator/receiver functions used for network management.
-
D.
RFC 3112
RFC 3112 is an Internet Engineering Task Force (IETF) standard that originally specified an authentication mechanism for the Lightweight Directory Access Protocol (LDAP).
-
E.
RFC 3491
RFC 3491 is an Internet standard that defines the Nameprep string preparation algorithm used to normalize internationalized domain names for consistent and secure processing.
- 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 3513 Triple: [RFC 4291, obsoletes, RFC 3513]
Generated description
RFC 3513 is an earlier Internet standard that defined the addressing architecture for IPv6 before being superseded by RFC 4291.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3513 Target entity description: RFC 3513 is an earlier Internet standard that defined the addressing architecture for IPv6 before being superseded by RFC 4291.
-
A.
RFC 3653
RFC 3653 is an Internet Engineering Task Force (IETF) standards-track document that specifies aspects of the Message Session Relay Protocol (MSRP) used for transmitting instant messages and related media over IP networks.
-
B.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
C.
RFC 3413
RFC 3413 is an Internet standard that specifies the Simple Network Management Protocol (SNMPv3) applications, including notification, proxy, and command generator/receiver functions used for network management.
-
D.
RFC 3112
RFC 3112 is an Internet Engineering Task Force (IETF) standard that originally specified an authentication mechanism for the Lightweight Directory Access Protocol (LDAP).
-
E.
RFC 3491
RFC 3491 is an Internet standard that defines the Nameprep string preparation algorithm used to normalize internationalized domain names for consistent and secure processing.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a0aa0ed88190b0198cbfd1bcc59b |
completed | April 29, 2026, 6:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0c5dd5ca4881909453c262d6ab9b1a |
completed | May 19, 2026, 12:55 p.m. |
| NEDg | Description generation | batch_6a0c61cdf14481909173cc65e16f2c82 |
completed | May 19, 2026, 1:12 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0c625b52248190ba3d59f42dd99da3 |
completed | May 19, 2026, 1:15 p.m. |
Created at: April 17, 2026, 5:30 p.m.