Triple
T7936191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WebDAV |
E184293
|
entity |
| Predicate | relatedStandard |
P37
|
FINISHED |
| Object | CardDAV |
E356947
|
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: CardDAV | Statement: [WebDAV, relatedStandard, CardDAV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CardDAV Context triple: [WebDAV, relatedStandard, CardDAV]
-
A.
CardDAV
chosen
CardDAV is an open standard protocol that enables remote access, synchronization, and management of contact data over the Web using HTTP and WebDAV.
-
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.
Cardfile
Cardfile is a simple card-based personal information manager included with early versions of Microsoft Windows for storing and organizing small text notes.
-
D.
Nextcloud Calendar
Nextcloud Calendar is an open-source, self-hosted calendar application that lets users manage and share events across devices while keeping full control over their data.
-
E.
vCard
vCard is a standardized file format for electronic business cards that stores and exchanges contact information such as names, phone numbers, addresses, and email details across different applications and devices.
- 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_69ca8290c21c8190906a5ca6fe2b03c4 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3aede3cc81908b0d3b54e68997b9 |
completed | March 31, 2026, 3:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5c0791e48190af18299c22f6a804 |
completed | March 31, 2026, 5:30 a.m. |
Created at: March 30, 2026, 5:08 p.m.