Triple
T12515485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4880 |
E299181
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2440 |
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: RFC 2440 | Statement: [RFC 4880, obsoletes, RFC 2440]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2440 Context triple: [RFC 4880, obsoletes, RFC 2440]
-
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 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
C.
RFC 2244
RFC 2244 is an Internet standards document that specifies the Application Configuration Access Protocol (ACAP), a protocol for remote storage and management of user and application configuration data.
-
D.
RFC 2048
RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
-
E.
RFC 2144
RFC 2144 is an Internet standards document that specifies the CAST-128 (CAST5) symmetric-key block cipher for use in cryptographic applications.
- 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_69f64bbd58b88190baeb99380babf64f |
completed | May 2, 2026, 7:08 p.m. |
Created at: April 8, 2026, 9:57 p.m.