Triple
T11801146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1869 |
E280627
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 1652 |
E230348
|
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 1652 | Statement: [RFC 1869, relatedTo, RFC 1652]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1652 Context triple: [RFC 1869, relatedTo, RFC 1652]
-
A.
RFC 1652
chosen
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.
-
B.
RFC 1662
RFC 1662 is an Internet Engineering Task Force (IETF) standard that specifies the framing for Point-to-Point Protocol (PPP) over synchronous and asynchronous serial links.
-
C.
RFC 1602
RFC 1602 was an earlier Internet standards process document that defined procedures for developing and standardizing Internet protocols before being superseded by RFC 2026.
-
D.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
-
E.
RFC 1642
RFC 1642 is an Internet standards document that defines the UTF-7 encoding for representing Unicode characters in environments restricted to 7-bit data.
- 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_69d6ab258b808190b1735835c841e3a4 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a5a4512c8190b7782e1dee053000 |
completed | April 10, 2026, 7:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f13129fa608190b080dc27f8bd7803 |
completed | April 28, 2026, 10:14 p.m. |
Created at: April 8, 2026, 9:42 p.m.