Triple
T1096872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ORTC |
E24289
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | real-time communications API |
C7025
|
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: real-time communications API Context triple: [ORTC, instanceOf, real-time communications API]
-
A.
speech recognition API
A speech recognition API is a software interface that converts spoken language into machine-readable text or commands, enabling applications to process and respond to voice input.
-
B.
instant messaging service
An instant messaging service is a platform that enables users to exchange real-time text, multimedia, and other data over the internet, often supporting presence indicators, group chats, and cross-device synchronization.
-
C.
communication protocol
A communication protocol is a defined set of rules and formats that enable reliable, structured exchange of data between two or more communicating entities in a networked system.
-
D.
asynchronous communication method
An asynchronous communication method is a way of exchanging information where messages are sent and received at different times, without requiring all participants to be simultaneously available.
-
E.
communications unit
A communications unit is a modular component responsible for managing, formatting, and transmitting information between systems, devices, or subsystems using defined communication protocols.
- 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_69a4940542308190ac2a0b1f730b7cfc |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:42 p.m.