Triple
T10447593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Building Protocols with HTTP |
E246333
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 3205 |
E863221
|
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 3205 | Statement: [Building Protocols with HTTP, obsoletes, RFC 3205]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3205 Context triple: [Building Protocols with HTTP, obsoletes, RFC 3205]
-
A.
RFC 3205
chosen
RFC 3205 is an informational Internet standard that provides guidelines and considerations for designing and deploying application protocols that use HTTP as a substrate.
-
B.
RFC 3207
RFC 3207 is the Internet standard that specifies the STARTTLS extension for upgrading plain text email connections to use TLS encryption in SMTP.
-
C.
RFC 3652
RFC 3652 is an IETF standards-track document that specifies the technical architecture and protocols of the Handle System for assigning, managing, and resolving persistent digital identifiers.
-
D.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
E.
RFC 3650
RFC 3650 is an IETF document that specifies the architectural framework and core concepts of the Handle System, a global identifier and resolution system for digital resources.
- 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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fdc10c8081908a3801fe1dea63de |
completed | April 7, 2026, 12:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d89fb27f5081909e78bd8029e65948 |
completed | April 10, 2026, 6:58 a.m. |
Created at: April 6, 2026, 12:16 p.m.