Triple
T5479008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2460 |
E123424
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | RFC 8200 |
E23862
|
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 8200 | Statement: [RFC 2460, successor, RFC 8200]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 8200 Context triple: [RFC 2460, successor, RFC 8200]
-
A.
RFC 8200
chosen
RFC 8200 is the Internet Engineering Task Force (IETF) standard that specifies the core protocol architecture and operation of Internet Protocol version 6 (IPv6).
-
B.
RFC 2460
RFC 2460 is the original Internet standard that specified the core IPv6 protocol header and packet format, later superseded by RFC 8200.
-
C.
RFC 8332
RFC 8332 is an Internet Engineering Task Force (IETF) standard that updates and replaces earlier SSH protocol specifications to enhance security and functionality.
-
D.
RFC 4271
RFC 4271 is the core Internet standards document that specifies the Border Gateway Protocol version 4 (BGP-4), which governs inter-domain routing between autonomous systems.
-
E.
RFC 8314
RFC 8314 is an Internet standard that specifies the use of mandatory encryption (TLS) for email submission and access protocols to improve the security of email communications.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd9247a16c8190ac5a02534da48853 |
completed | March 20, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf6c7a61848190970a4e34696791eb |
completed | March 22, 2026, 4:13 a.m. |
Created at: March 20, 2026, 2:09 p.m.