Triple
T13636431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1042 |
E325859
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 894 |
E752944
|
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 894 | Statement: [RFC 1042, obsoletedBy, RFC 894]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 894 Context triple: [RFC 1042, obsoletedBy, RFC 894]
-
A.
RFC 894
chosen
RFC 894 is an Internet standard that specifies how IP datagrams are encapsulated for transmission over Ethernet networks.
-
B.
RFC 879
RFC 879 is an early Internet standard document that specifies details of the Transmission Control Protocol (TCP), contributing to the foundational design of reliable transport on the Internet.
-
C.
RFC 1094
RFC 1094 is the original specification document that standardizes the Network File System (NFS) protocol used for remote file access over a network.
-
D.
RFC 974
RFC 974 is an early Internet standard that defined the original mechanisms for mail routing and the use of MX records in the Domain Name System (DNS).
-
E.
RFC 1889
RFC 1889 was the original specification of the Real-time Transport Protocol (RTP) for delivering audio and video over IP networks, later obsoleted by updated standards.
- 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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5a616dc81908b8c1213e1d4beed |
completed | April 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78af297008190b12256c936714213 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:51 p.m.