Triple
T9731963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1654 |
E235766
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 1661 |
E250392
|
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 1661 | Statement: [RFC 1654, obsoletedBy, RFC 1661]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1661 Context triple: [RFC 1654, obsoletedBy, RFC 1661]
-
A.
RFC 1661
chosen
RFC 1661 is the original specification of the Point-to-Point Protocol (PPP), defining a standard method for transporting multi-protocol datagrams over point-to-point links.
-
B.
RFC 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
C.
RFC 1660
RFC 1660 is an early Internet standards document that specified an initial version of the Simple Network Management Protocol (SNMP) over OSI transport services before being superseded by later RFCs.
-
D.
RFC 1665
RFC 1665 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
E.
RFC 1652
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
- 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_69ca84d0fad481909cdd45aa77416c48 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9eb3d6e4819090b3c7fb92550c57 |
completed | April 1, 2026, 10:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1afba5ec081908044a4aefdc6f9ee |
completed | April 5, 2026, 12:41 a.m. |
Created at: March 30, 2026, 8:22 p.m.