Triple
T10158985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2811 |
E233839
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 2813 |
E825153
|
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 2813 | Statement: [RFC 2811, relatedTo, RFC 2813]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2813 Context triple: [RFC 2811, relatedTo, RFC 2813]
-
A.
RFC 2813
chosen
RFC 2813 is an Internet standards document that specifies the server-to-server protocol for the Internet Relay Chat (IRC) network.
-
B.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
C.
RFC 1663
RFC 1663 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for serial line communication.
-
D.
RFC 2811
RFC 2811 is an Internet standards document that specifies the architecture and operation of Internet Relay Chat (IRC) channel management.
-
E.
RFC 2830
RFC 2830 is an Internet standard that originally specified how to use Transport Layer Security (TLS) to secure LDAP (Lightweight Directory Access Protocol) connections.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec56d944819081bc6ea36c905ba2 |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d65296ee98819096de701e3b945001 |
completed | April 8, 2026, 1:05 p.m. |
Created at: March 30, 2026, 9:09 p.m.