Triple
T10158248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4512 |
E233824
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2830 |
E821315
|
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 2830 | Statement: [RFC 4512, obsoletes, RFC 2830]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2830 Context triple: [RFC 4512, obsoletes, RFC 2830]
-
A.
RFC 2830
chosen
RFC 2830 is an Internet standard that originally specified how to use Transport Layer Security (TLS) to secure LDAP (Lightweight Directory Access Protocol) connections.
-
B.
RFC 2870
RFC 2870 is an Internet Engineering Task Force (IETF) document that specifies operational and technical requirements for the DNS root name server system.
-
C.
RFC 2030
RFC 2030 is an Internet Engineering Task Force (IETF) specification that defined the Simple Network Time Protocol (SNTP) for clock synchronization over IP networks.
-
D.
RFC 2813
RFC 2813 is an Internet standards document that specifies the server-to-server protocol for the Internet Relay Chat (IRC) network.
-
E.
RFC 3380
RFC 3380 is an Internet Engineering Task Force (IETF) document that defines additional features and extensions for the Internet Printing Protocol (IPP).
- 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_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d32ac043f08190ba7f526d226d3c8c |
completed | April 6, 2026, 3:38 a.m. |
Created at: March 30, 2026, 9:09 p.m.