Triple
T22027201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6156 |
E543997
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 5766 |
—
|
NE NERFINISHED |
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 5766 | Statement: [RFC 6156, obsoletes, RFC 5766]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5766 Context triple: [RFC 6156, obsoletes, RFC 5766]
-
A.
RFC 5766
chosen
RFC 5766 is an IETF specification that defines the Traversal Using Relays around NAT (TURN) protocol for relaying network traffic to help clients communicate across NATs and firewalls.
-
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 4516
RFC 4516 is an Internet standard that specifies the LDAP (Lightweight Directory Access Protocol) Uniform Resource Locator (URL) format used to locate and access directory entries over a network.
-
D.
RFC 2866
RFC 2866 is an IETF specification that defines the accounting extensions for the RADIUS (Remote Authentication Dial-In User Service) protocol used in network access and usage tracking.
-
E.
RFC 2732
RFC 2732 is an Internet standards document that specified the use of bracketed IPv6 addresses in URLs before being superseded by RFC 3986.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ccc2ec8190a94d69530d00c06c |
completed | April 28, 2026, 9:34 p.m. |
Created at: April 16, 2026, 8:24 p.m.