Triple
T22430047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 6860 |
E554473
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 2328 |
—
|
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 2328 | Statement: [RFC 6860, relatedTo, RFC 2328]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2328 Context triple: [RFC 6860, relatedTo, RFC 2328]
-
A.
RFC 2328
chosen
RFC 2328 is the Internet Engineering Task Force (IETF) standard that specifies version 2 of the Open Shortest Path First (OSPFv2) interior gateway routing protocol used in IP networks.
-
B.
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.
-
C.
RFC 2327
RFC 2327 is the original IETF specification that defines the Session Description Protocol (SDP) used to describe multimedia communication sessions for purposes such as session announcement and invitation.
-
D.
RFC 2810
RFC 2810 is an Internet standards document that specifies the architecture and core concepts of the Internet Relay Chat (IRC) protocol.
-
E.
RFC 2451
RFC 2451 is an Internet Engineering Task Force (IETF) standard that specifies how to use the Twofish encryption algorithm within the IPsec protocol suite for secure network communications.
- 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_69e11e4f2d0c819091aa3558ea2ee630 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15a311b148190bdb752f3f067bb3f |
completed | April 29, 2026, 1:09 a.m. |
Created at: April 16, 2026, 8:47 p.m.