Triple
T3420821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iCalendar |
E72110
|
entity |
| Predicate | definedInRFC |
P5655
|
FINISHED |
| Object |
RFC 5545
RFC 5545 is the Internet standards document that specifies the iCalendar data format used for exchanging calendaring and scheduling information.
|
E72110
|
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 5545 | Statement: [iCalendar, definedInRFC, RFC 5545]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 5545 Context triple: [iCalendar, definedInRFC, RFC 5545]
-
A.
iCalendar
iCalendar is a widely used open standard file format for exchanging calendar and scheduling information across different applications and services.
-
B.
CalDAV
CalDAV is an open standard protocol that allows clients to access, manage, and synchronize calendar data on a remote server over WebDAV.
-
C.
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.
-
D.
RFC 4518
RFC 4518 is an Internet standard that specifies string preparation and comparison rules for use in LDAP directories.
-
E.
RFC 6120
RFC 6120 is an IETF standard that defines the core XML streaming and authentication framework for the Extensible Messaging and Presence Protocol (XMPP).
- 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 5545 Triple: [iCalendar, definedInRFC, RFC 5545]
Generated description
RFC 5545 is the Internet standards document that specifies the iCalendar data format used for exchanging calendaring and scheduling information.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 5545 Target entity description: RFC 5545 is the Internet standards document that specifies the iCalendar data format used for exchanging calendaring and scheduling information.
-
A.
iCalendar
chosen
iCalendar is a widely used open standard file format for exchanging calendar and scheduling information across different applications and services.
-
B.
CalDAV
CalDAV is an open standard protocol that allows clients to access, manage, and synchronize calendar data on a remote server over WebDAV.
-
C.
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.
-
D.
RFC 4518
RFC 4518 is an Internet standard that specifies string preparation and comparison rules for use in LDAP directories.
-
E.
RFC 6120
RFC 6120 is an IETF standard that defines the core XML streaming and authentication framework for the Extensible Messaging and Presence Protocol (XMPP).
- F. None of above.
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_69ad85ad38e48190b7660c5118a35289 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb94eb9e8819087a525df4550914b |
completed | March 8, 2026, 6 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b354701e908190a8a7f14ae578fa5d |
completed | March 13, 2026, 12:04 a.m. |
| NEDg | Description generation | batch_69b358c7970881909b20126ba170495d |
completed | March 13, 2026, 12:22 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69b35930c3808190a3d9cbc69a26a1c1 |
completed | March 13, 2026, 12:24 a.m. |
Created at: March 8, 2026, 3:15 p.m.