Triple
T10024793
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2817 |
E200697
|
entity |
| Predicate | relatedTo |
P37
|
FINISHED |
| Object | RFC 2616 |
E290849
|
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 2616 | Statement: [RFC 2817, relatedTo, RFC 2616]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2616 Context triple: [RFC 2817, relatedTo, RFC 2616]
-
A.
RFC 2616
chosen
RFC 2616 is the IETF specification that defined HTTP/1.1, standardizing the core semantics and behavior of the Hypertext Transfer Protocol used on the web.
-
B.
RFC 2068
RFC 2068 is an early Internet standards document that specifies the HTTP/1.1 protocol, detailing its methods, headers, and overall message structure for web communication.
-
C.
RFC 7231
RFC 7231 is an IETF specification that defined the semantics and content of the HTTP/1.1 protocol, including methods, status codes, and header fields, before being superseded by RFC 9112.
-
D.
RFC 2623
RFC 2623 was an early Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4250.
-
E.
RFC 7230
RFC 7230 is an IETF standard that specifies the core message syntax and routing semantics for the Hypertext Transfer Protocol (HTTP/1.1), including its use over secure transport like HTTPS.
- 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd7d9c9c81909a0a0917deed0973 |
completed | April 2, 2026, 1:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d26ac2f14081908deaf3945491af78 |
completed | April 5, 2026, 1:59 p.m. |
Created at: March 30, 2026, 8:53 p.m.