Triple
T271019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1035 |
E5631
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 1034 |
E35279
|
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 1034 | Statement: [RFC 1035, relatedTo, RFC 1034]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1034 Context triple: [RFC 1035, relatedTo, RFC 1034]
-
A.
RFC 1034
chosen
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.
-
B.
RFC 1035
RFC 1035 is an Internet standards document that defines the implementation details, message formats, and operational procedures for the Domain Name System (DNS).
-
C.
RFC 1939
RFC 1939 is the Internet standard document that specifies the Post Office Protocol version 3 (POP3) used for retrieving email from a mail server.
-
D.
RFC 2131
RFC 2131 is the Internet Engineering Task Force (IETF) standard that specifies the Dynamic Host Configuration Protocol (DHCP) used for automatic IP address and configuration assignment in IP networks.
-
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_69a25853594c8190b05ec3a586ec88bf |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25db17e8c8190a6ebcadd8a0abf4d |
completed | Feb. 28, 2026, 3:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3914eba9081908cdef8b719c9b20b |
completed | March 1, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 2:57 a.m.