Triple
T4575435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UTF-7 |
E123130
|
entity |
| Predicate | deprecatedIn |
P1466
|
FINISHED |
| Object |
RFC 3986
RFC 3986 is the Internet standard that defines the syntax and semantics of Uniform Resource Identifiers (URIs), superseding earlier URI specifications.
|
E453731
|
NE FINISHED |
How this triple was built (4 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 3986 | Statement: [UTF-7, deprecatedIn, RFC 3986]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3986 Context triple: [UTF-7, deprecatedIn, RFC 3986]
-
A.
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.
-
B.
RFC 2616
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.
-
C.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
D.
RFC 9110
RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
-
E.
RFC 4627
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 3986 Triple: [UTF-7, deprecatedIn, RFC 3986]
Generated description
RFC 3986 is the Internet standard that defines the syntax and semantics of Uniform Resource Identifiers (URIs), superseding earlier URI specifications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3986 Target entity description: RFC 3986 is the Internet standard that defines the syntax and semantics of Uniform Resource Identifiers (URIs), superseding earlier URI specifications.
-
A.
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.
-
B.
RFC 2616
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.
-
C.
RFC 7234
RFC 7234 is an IETF specification that defines HTTP/1.1 caching semantics, including how responses may be stored, reused, and validated by caches.
-
D.
RFC 9110
RFC 9110 is an IETF specification that defines the core semantics and architecture of the Hypertext Transfer Protocol (HTTP).
-
E.
RFC 4627
RFC 4627 is the original IETF specification that formally defined the JSON (JavaScript Object Notation) data interchange format.
- F. None of above. chosen
Provenance (5 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58dfe3508190b21836079e951a3c |
completed | March 20, 2026, 2:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bdd3e656a08190bb48d2ecae1eb798 |
completed | March 20, 2026, 11:10 p.m. |
| NEDg | Description generation | batch_69bdd71b55d8819085340c8abb9c369e |
completed | March 20, 2026, 11:24 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69bdd78c9a008190b774db2742a3b371 |
completed | March 20, 2026, 11:26 p.m. |
Created at: March 20, 2026, 1:10 p.m.