Triple
T12515563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2440 |
E299182
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object | RFC2440 |
E299182
|
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: RFC2440 | Statement: [RFC 2440, hasAbbreviation, RFC2440]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC2440 Context triple: [RFC 2440, hasAbbreviation, RFC2440]
-
A.
RFC 2440
chosen
RFC 2440 is the Internet Engineering Task Force (IETF) specification that defines the OpenPGP message format for encrypted and signed data.
-
B.
RFC 2048
RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
-
C.
RFC 2049
RFC 2049 is an Internet standards document that defines the conformance, operational considerations, and security issues for the MIME (Multipurpose Internet Mail Extensions) specification used in Internet email.
-
D.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
E.
RFC 4254
RFC 4254 is the Internet standard that specifies the Secure Shell (SSH) connection protocol, defining how multiple logical channels are multiplexed over a single encrypted SSH transport.
- 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9541f80148190976d1d912fe155d0 |
completed | April 10, 2026, 7:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f655745cec8190b5582eb4a339d501 |
completed | May 2, 2026, 7:50 p.m. |
Created at: April 8, 2026, 9:57 p.m.