Triple
T7297486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Mockapetris |
E164560
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object | RFC 883 |
E37188
|
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 883 | Statement: [Paul Mockapetris, standardizedIn, RFC 883]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 883 Context triple: [Paul Mockapetris, standardizedIn, RFC 883]
-
A.
RFC 883
chosen
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
-
B.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
-
C.
RFC 783
RFC 783 is the original specification that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
D.
RFC 862
RFC 862 is an Internet standard that specifies the Echo Protocol, a simple service used primarily for testing and measurement by sending data to a server that returns it unchanged.
-
E.
RFC 855
RFC 855 is an Internet standards document that specifies the Telnet protocol’s options and mechanisms for remote terminal communication over TCP/IP networks.
- 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_69c6887a499881909dd23341399c59d8 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6eb8e48d48190ada4d507f3b61bc4 |
completed | March 27, 2026, 8:41 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7eee330e08190b39bdf3f5071cace |
completed | March 28, 2026, 3:08 p.m. |
Created at: March 27, 2026, 3 p.m.