Triple
T32422479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Feishu |
E828493
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | enterprise messaging platform |
C52159
|
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: enterprise messaging platform Context triple: [Feishu, instanceOf, enterprise messaging platform]
-
A.
enterprise collaboration product
chosen
An enterprise collaboration product is a software platform that enables employees and teams within an organization to communicate, share information, and coordinate work efficiently and securely.
-
B.
customer communication tool
A customer communication tool is a system that enables businesses to manage, streamline, and track interactions with customers across multiple channels such as email, chat, social media, and SMS.
-
C.
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.
-
D.
real-time communication service
A real-time communication service enables instantaneous, bidirectional exchange of data—such as messages, audio, or video—between clients over a network with minimal latency.
-
E.
unified communications software
Unified communications software is an integrated platform that combines voice, video, messaging, and collaboration tools into a single interface to streamline business communication and teamwork.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:54 a.m.