Triple
T9690785
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5905 |
E234528
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2030
RFC 2030 is an Internet Engineering Task Force (IETF) specification that defined the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
|
E815698
|
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 2030 | Statement: [RFC 5905, obsoletes, RFC 2030]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2030 Context triple: [RFC 5905, obsoletes, RFC 2030]
-
A.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
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 2910
RFC 2910 is an IETF specification that defines the Internet Printing Protocol/1.1 model and encoding for network printing.
-
D.
RFC 3090
RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
-
E.
RFC 2069
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
- 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 2030 Triple: [RFC 5905, obsoletes, RFC 2030]
Generated description
RFC 2030 is an Internet Engineering Task Force (IETF) specification that defined the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2030 Target entity description: RFC 2030 is an Internet Engineering Task Force (IETF) specification that defined the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
-
A.
RFC 1730
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
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 2910
RFC 2910 is an IETF specification that defines the Internet Printing Protocol/1.1 model and encoding for network printing.
-
D.
RFC 3090
RFC 3090 is an earlier Internet Engineering Task Force (IETF) standards document related to the Domain Name System (DNS) that was later superseded by RFC 4035.
-
E.
RFC 2069
RFC 2069 is an early IETF specification that defined a digest access authentication mechanism for HTTP, later superseded by RFC 2617.
- 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d0422e88190a234ba74eb0dad25 |
completed | April 1, 2026, 10:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d19118874c81909a97f874b1dc2db8 |
completed | April 4, 2026, 10:30 p.m. |
| NEDg | Description generation | batch_69d193a5cdac8190b84564f397d00124 |
completed | April 4, 2026, 10:41 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69d19457c6488190a7bc72e1a27c088a |
completed | April 4, 2026, 10:44 p.m. |
Created at: March 30, 2026, 8:17 p.m.