Triple
T25535651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayday live support |
E640031
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | on-device assistance feature |
C23821
|
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: on-device assistance feature Context triple: [Mayday live support, instanceOf, on-device assistance feature]
-
A.
smartphone hardware feature
A smartphone hardware feature is a physical component or built-in device capability—such as a camera, fingerprint sensor, or NFC chip—that enables specific functions and interactions on a smartphone.
-
B.
mobile operating system feature
chosen
A mobile operating system feature is a built-in software capability or service within a smartphone or tablet OS that enhances device functionality, user interaction, performance, or security.
-
C.
mobile application feature
A mobile application feature is a distinct, user-facing capability or function within a mobile app that enables users to perform specific tasks or achieve particular goals.
-
D.
feature phone
A feature phone is a mobile device that offers basic calling and texting capabilities along with limited multimedia and internet functions, without the advanced operating systems and app ecosystems of smartphones.
-
E.
voice application platform feature
A voice application platform feature is a functional capability within a voice-enabled system that allows developers or users to create, manage, and enhance interactive voice experiences through tools like speech recognition, natural language understanding, and integration with external services.
- F. None of above.
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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 3:22 p.m.