Triple
T9690937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NTP Autokey |
E234531
|
entity |
| Predicate | documentedIn |
P309
|
FINISHED |
| Object | RFC 5906 |
E815701
|
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 5906 | Statement: [NTP Autokey, documentedIn, RFC 5906]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5906 Context triple: [NTP Autokey, documentedIn, RFC 5906]
-
A.
RFC 5906
chosen
RFC 5906 is an Internet Engineering Task Force (IETF) standard that specifies Network Time Protocol (NTP) authentication using Autokey public key cryptography.
-
B.
RFC 6066
RFC 6066 is an Internet Engineering Task Force (IETF) standard that specifies Transport Layer Security (TLS) extensions, including the widely used Server Name Indication (SNI) extension.
-
C.
RFC 5996
RFC 5996 is an Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange Protocol version 2 (IKEv2) for establishing secure IPsec connections.
-
D.
RFC 6096
RFC 6096 is an Internet Engineering Task Force (IETF) standards document that refines and updates the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
-
E.
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.
- 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_69d1bcbbe0108190a7011d52ba24ba4b |
completed | April 5, 2026, 1:37 a.m. |
Created at: March 30, 2026, 8:17 p.m.