Triple
T14424270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vCalendar |
E357654
|
entity |
| Predicate | successor |
P78
|
FINISHED |
| Object | iCalendar |
E72110
|
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: iCalendar | Statement: [vCalendar, successor, iCalendar]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: iCalendar Context triple: [vCalendar, successor, iCalendar]
-
A.
iCalendar
chosen
iCalendar is a widely used open standard file format for exchanging calendar and scheduling information across different applications and services.
-
B.
vCalendar
vCalendar is an early electronic calendaring and scheduling format that served as a predecessor to the more widely adopted iCalendar standard.
-
C.
CalDAV
CalDAV is an open standard protocol that allows clients to access, manage, and synchronize calendar data on a remote server over WebDAV.
-
D.
iTIP
iTIP (iCalendar Transport-Independent Interoperability Protocol) is a protocol that defines how calendar and scheduling information is exchanged between systems using iCalendar data.
-
E.
Calendaring and Scheduling (calsify)
Calendaring and Scheduling (calsify) is an IETF working group focused on developing and maintaining Internet standards for interoperable electronic calendaring and scheduling.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91123f848190ba3fb18a76c2d24c |
completed | April 14, 2026, 7:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fda90a7f2881909a7744f1f4344173 |
completed | May 8, 2026, 9:12 a.m. |
Created at: April 10, 2026, 1:18 a.m.