Triple
T9690846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1305 |
E234529
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 5905 |
E234528
|
NE FINISHED |
How this triple was built (2 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 5905 | Statement: [RFC 1305, obsoletedBy, RFC 5905]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5905 Context triple: [RFC 1305, obsoletedBy, RFC 5905]
-
A.
RFC 5905
chosen
RFC 5905 is the Internet standard specification that defines version 4 of the Network Time Protocol (NTP) for synchronizing clocks over packet-switched, variable-latency data networks.
-
B.
RFC 5906
RFC 5906 is an Internet Engineering Task Force (IETF) standard that specifies Network Time Protocol (NTP) authentication using Autokey public key cryptography.
-
C.
RFC 5907
RFC 5907 is an Internet Engineering Task Force (IETF) document that defines management information base (MIB) modules for monitoring and managing the Network Time Protocol (NTP) as specified in RFC 5905.
-
D.
RFC 3995
RFC 3995 is an IETF specification that defines the Event Notifications extension for the Internet Printing Protocol (IPP), enabling printers and print services to send asynchronous status and alert messages to clients.
-
E.
RFC 9205
RFC 9205 is an IETF specification that provides guidance and best practices for the use and deployment of HTTP, complementing the core protocol definitions in related HTTP RFCs.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d1af80358881909cdd91f2aed33ef6 |
completed | April 5, 2026, 12:40 a.m. |
Created at: March 30, 2026, 8:17 p.m.