Triple
T868560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 8601 |
E18759
|
entity |
| Predicate | influenced |
P9
|
FINISHED |
| Object |
RFC 3339
RFC 3339 is an Internet standard that defines a simplified, unambiguous date and time format commonly used in internet protocols and data interchange.
|
E100895
|
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 3339 | Statement: [ISO 8601, influenced, RFC 3339]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3339 Context triple: [ISO 8601, influenced, RFC 3339]
-
A.
ISO 8601
ISO 8601 is an international standard that defines a consistent, unambiguous format for representing dates, times, and related data in numeric form.
-
B.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
-
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 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
-
E.
RFC 9002
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
- 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 3339 Triple: [ISO 8601, influenced, RFC 3339]
Generated description
RFC 3339 is an Internet standard that defines a simplified, unambiguous date and time format commonly used in internet protocols and data interchange.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 3339 Target entity description: RFC 3339 is an Internet standard that defines a simplified, unambiguous date and time format commonly used in internet protocols and data interchange.
-
A.
ISO 8601
ISO 8601 is an international standard that defines a consistent, unambiguous format for representing dates, times, and related data in numeric form.
-
B.
RFC 7233
RFC 7233 was an HTTP/1.1 specification that defined range requests and partial content delivery mechanisms for HTTP resources.
-
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 7232
RFC 7232 is an HTTP/1.1 specification that defines conditional request mechanisms using validators like ETags and Last-Modified to support efficient caching and concurrency control on the web.
-
E.
RFC 9002
RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7f98908190883f71049092c7c8 |
completed | March 1, 2026, 9:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a7a3c9e7ec819081d58634fe0efdcb |
completed | March 4, 2026, 3:15 a.m. |
| NEDg | Description generation | batch_69a7a44c2d5881909d006ddf9f9ed694 |
completed | March 4, 2026, 3:17 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69a7a4a811bc819093bd436de45afa97 |
completed | March 4, 2026, 3:19 a.m. |
Created at: March 1, 2026, 7:39 p.m.