Triple
T14370763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DAViCal |
E356352
|
entity |
| Predicate | supportsStandard |
P1587
|
FINISHED |
| Object | WebDAV |
E184293
|
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: WebDAV | Statement: [DAViCal, supportsStandard, WebDAV]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: WebDAV Context triple: [DAViCal, supportsStandard, WebDAV]
-
A.
WebDAV
chosen
WebDAV (Web Distributed Authoring and Versioning) is an extension of the HTTP protocol that enables collaborative editing and file management on remote web servers.
-
B.
WebHDFS REST API
WebHDFS REST API is an HTTP-based interface that allows applications to interact with and manage data stored in Hadoop Distributed File System (HDFS) over the web.
-
C.
RFC 4918
RFC 4918 is the IETF specification that standardizes the Web Distributed Authoring and Versioning (WebDAV) extensions to HTTP for collaborative web content authoring and file management.
-
D.
Filestore
Filestore is a managed network file storage service on Google Cloud that provides scalable, high-performance file systems for applications running in the cloud.
-
E.
Directory Access Protocol
Directory Access Protocol (DAP) is an OSI-standard network protocol used to access and manage directory services, serving as a predecessor and conceptual basis for LDAP.
- 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_69d8279163a081908aec45c0e3f1e02f |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8fb0b8988190ab834a85911c015c |
completed | April 14, 2026, 7:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd5bbf21a48190921e99685c7ef2b9 |
completed | May 8, 2026, 3:42 a.m. |
Created at: April 10, 2026, 1:15 a.m.