Triple
T9312836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7720 |
E224045
|
entity |
| Predicate | updates |
P4061
|
FINISHED |
| Object | RFC 2870 |
E224046
|
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 2870 | Statement: [RFC 7720, updates, RFC 2870]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2870 Context triple: [RFC 7720, updates, RFC 2870]
-
A.
RFC 2870
chosen
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
B.
RFC 2865
RFC 2865 is the IETF standard that specifies the Remote Authentication Dial-In User Service (RADIUS) protocol for centralized authentication, authorization, and accounting in network access.
-
C.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
D.
RFC 1870
RFC 1870 is an earlier Internet standards document that defined support for extended SMTP message sizes before being superseded by RFC 2821.
-
E.
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.
- 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_69ca8425f4fc81909c1c586e9a5b7530 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd20ae96e481909a1af9ea1c91f2b2 |
completed | April 1, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d0c797640c8190be003e321faf3b86 |
completed | April 4, 2026, 8:11 a.m. |
Created at: March 30, 2026, 7:37 p.m.