Triple
T11033259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2623 |
E260811
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | RFC 2623 |
E260811
|
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 2623 | Statement: [RFC 2623, abbreviation, RFC 2623]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2623 Context triple: [RFC 2623, abbreviation, RFC 2623]
-
A.
RFC 2623
chosen
RFC 2623 was an early Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4250.
-
B.
RFC 2633
RFC 2633 is an earlier Internet standards document that specified the original S/MIME Version 3 message specification for secure email before being superseded by RFC 5751.
-
C.
RFC 2203
RFC 2203 is an Internet standard that specifies the RPCSEC_GSS security protocol extension for providing authentication, integrity, and confidentiality in Remote Procedure Call (RPC) systems using GSS-API.
-
D.
RFC 1662
RFC 1662 is an Internet Engineering Task Force (IETF) standard that specifies the framing for Point-to-Point Protocol (PPP) over synchronous and asynchronous serial links.
-
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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e650b48190967c53f54e3464ad |
completed | April 9, 2026, 12:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3a9a6db688190a740b787448d97b2 |
completed | April 18, 2026, 3:56 p.m. |
Created at: April 8, 2026, 9:25 p.m.