Triple
T21191293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOBIKE |
E522216
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object | RFC 4555 |
—
|
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 4555 | Statement: [MOBIKE, standardizedIn, RFC 4555]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4555 Context triple: [MOBIKE, standardizedIn, RFC 4555]
-
A.
RFC 4555
chosen
RFC 4555 is an Internet Engineering Task Force (IETF) specification that defines the MOBIKE (IKEv2 Mobility and Multihoming) protocol extensions for the IKEv2 key management protocol.
-
B.
RFC 5155
RFC 5155 is an Internet standards document that specifies the NSEC3 extension to DNSSEC, enhancing DNS security by providing authenticated denial of existence while mitigating zone enumeration.
-
C.
RFC 3655
RFC 3655 is an Internet Engineering Task Force (IETF) document that was an earlier specification later superseded by the DNS Security (DNSSEC)–related standard defined in RFC 4033.
-
D.
RFC 5045
RFC 5045 is an IETF standard that defines the protocol mechanisms for implementing iWARP, enabling RDMA (Remote Direct Memory Access) over TCP/IP networks.
-
E.
RFC 3445
RFC 3445 is an earlier Internet Engineering Task Force (IETF) specification related to DNS security that was later superseded by RFC 4033.
- 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_69e733381f288190b3da795f62a39568 |
completed | April 21, 2026, 8:20 a.m. |
Created at: April 16, 2026, 3:07 p.m.