Triple
T13636715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2401 |
E325865
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 2409 |
E700398
|
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 2409 | Statement: [RFC 2401, relatedTo, RFC 2409]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2409 Context triple: [RFC 2401, relatedTo, RFC 2409]
-
A.
RFC 2409
chosen
RFC 2409 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Key Exchange (IKE) protocol used to establish secure, authenticated keying material for IPsec.
-
B.
RFC 2401
RFC 2401 is an Internet Engineering Task Force (IETF) standard that defines the Security Architecture for the Internet Protocol, forming the core specification for IPsec.
-
C.
RFC 4301
RFC 4301 is an IETF standard that defines the Security Architecture for IP, including the core framework and mechanisms for IPsec-based network security.
-
D.
RFC 3412
RFC 3412 is an Internet standard that specifies the message processing and dispatching procedures for the Simple Network Management Protocol (SNMP) within the SNMPv3 framework.
-
E.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5a616dc81908b8c1213e1d4beed |
completed | April 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78af297008190b12256c936714213 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:51 p.m.