Triple
T22375505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vCard |
E553142
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | electronic business card format |
C46192
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: electronic business card format Context triple: [vCard, instanceOf, electronic business card format]
-
A.
electronic calendaring format
An electronic calendaring format is a standardized digital structure for representing, storing, and exchanging calendar-related data such as events, tasks, and scheduling information across software systems.
-
B.
electronic signature platform
An electronic signature platform is a digital system that enables users to securely sign, send, and manage documents online while ensuring legal compliance and auditability.
-
C.
card-based database program
A card-based database program is a software application that organizes, stores, and manages information as individual "cards" or records, each containing related fields of data that can be easily viewed, edited, sorted, and searched.
-
D.
contact-type smart card
A contact-type smart card is a plastic card with an embedded integrated circuit chip that must physically connect to a reader via metallic contacts to securely store, process, and exchange data for applications like payments and identification.
-
E.
electronic payment system
An electronic payment system is a digital infrastructure that enables the secure transfer of funds between parties via electronic devices and networks without the need for physical cash or paper-based instruments.
- F. None of above. chosen
Provenance (1 batch)
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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.