Triple
T10069125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2060 |
E213172
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 1730 |
E282852
|
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 1730 | Statement: [RFC 2060, obsoletes, RFC 1730]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1730 Context triple: [RFC 2060, obsoletes, RFC 1730]
-
A.
RFC 1730
chosen
RFC 1730 is an early specification of the Internet Message Access Protocol (IMAP) that was later superseded by RFC 3501.
-
B.
RFC 1670
RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
-
C.
RFC 1870
RFC 1870 is an earlier Internet standards document that defined support for extended SMTP message sizes before being superseded by RFC 2821.
-
D.
RFC 1700
RFC 1700 is an Internet standards document that served as the central Assigned Numbers registry, cataloging protocol parameters such as port numbers, protocol numbers, and other key Internet identifiers.
-
E.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
- 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcff8d9c08190bc030f1dcc696310 |
completed | April 2, 2026, 2:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2b63d13fc8190bdeac3c7b2529052 |
completed | April 5, 2026, 7:21 p.m. |
Created at: March 30, 2026, 8:58 p.m.