Triple
T1425080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Mockapetris |
E30310
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object | RFC 1035 |
E5631
|
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 1035 | Statement: [Paul Mockapetris, standardizedIn, RFC 1035]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1035 Context triple: [Paul Mockapetris, standardizedIn, RFC 1035]
-
A.
RFC 1035
chosen
RFC 1035 is an Internet standards document that defines the implementation details, message formats, and operational procedures for the Domain Name System (DNS).
-
B.
RFC 1034
RFC 1034 is an Internet standards document that specifies the concepts and facilities of the Domain Name System (DNS), defining how domain names are structured and resolved on the internet.
-
C.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
D.
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.
-
E.
RFC 2132
RFC 2132 is an Internet Engineering Task Force (IETF) standard that specifies the DHCP options and BOOTP vendor extensions used for configuring network clients.
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c4bd59148190b96f9f585e07aa0d |
completed | March 1, 2026, 10:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad08b35da08190b8c09ad393f310e3 |
completed | March 8, 2026, 5:27 a.m. |
Created at: March 1, 2026, 8 p.m.