Triple
T21191114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2406 |
E522212
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 4303 |
—
|
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 4303 | Statement: [RFC 2406, obsoletedBy, RFC 4303]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4303 Context triple: [RFC 2406, obsoletedBy, RFC 4303]
-
A.
RFC 4303
chosen
RFC 4303 is an IETF standard that defines the Encapsulating Security Payload (ESP) protocol used to provide confidentiality, integrity, and authentication services in IPsec.
-
B.
RFC 2453
RFC 2453 is the Internet Engineering Task Force (IETF) standard that specifies the operation and protocol details of the Routing Information Protocol (RIP) for IP networks.
-
C.
RFC 4273
RFC 4273 is an Internet Engineering Task Force (IETF) standards document that defines the Management Information Base (MIB) for the Border Gateway Protocol version 4 (BGP-4), updating and replacing earlier BGP MIB specifications.
-
D.
RFC 3410
RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
-
E.
RFC 4330
RFC 4330 is an Internet Engineering Task Force (IETF) specification that defines a simple network time protocol (SNTP) for synchronizing computer clocks over IP networks.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733372b488190920174955b4b9172 |
completed | April 21, 2026, 8:20 a.m. |
Created at: April 16, 2026, 3:07 p.m.