Triple
T9865290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4517 |
E239816
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
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).
|
E826113
|
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 3112 | Statement: [RFC 4517, obsoletes, RFC 3112]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3112 Context triple: [RFC 4517, obsoletes, RFC 3112]
-
A.
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.
-
B.
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.
-
C.
RFC 3232
RFC 3232 is an IETF document that provides the current list of assigned Internet protocol numbers and related parameters, updating and replacing earlier registries.
-
D.
RFC 1812
RFC 1812 is an Internet standards document that defines the requirements and behavior for IPv4 routers in the Internet protocol suite.
-
E.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
- 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 3112 Triple: [RFC 4517, obsoletes, RFC 3112]
Generated description
RFC 3112 is an Internet Engineering Task Force (IETF) standard that originally specified an authentication mechanism for the Lightweight Directory Access Protocol (LDAP).
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3112 Target entity description: RFC 3112 is an Internet Engineering Task Force (IETF) standard that originally specified an authentication mechanism for the Lightweight Directory Access Protocol (LDAP).
-
A.
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.
-
B.
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.
-
C.
RFC 3232
RFC 3232 is an IETF document that provides the current list of assigned Internet protocol numbers and related parameters, updating and replacing earlier registries.
-
D.
RFC 1812
RFC 1812 is an Internet standards document that defines the requirements and behavior for IPv4 routers in the Internet protocol suite.
-
E.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
- 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_69ca84e7506c819095cbde4ff16512bb |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3ba7f288190a15ebec2cc3112c4 |
completed | April 2, 2026, 12:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1e44dc0b8819082294a479299814e |
completed | April 5, 2026, 4:25 a.m. |
| NEDg | Description generation | batch_69d1e4a42ab0819085150f033c2a650a |
completed | April 5, 2026, 4:27 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d1e50b803081909cd93a602fb48514 |
completed | April 5, 2026, 4:28 a.m. |
Created at: March 30, 2026, 8:36 p.m.