Triple
T19469537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Meet Group |
E487085
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | social entertainment company |
C24839
|
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: social entertainment company Context triple: [The Meet Group, instanceOf, social entertainment company]
-
A.
leisure and entertainment company
A leisure and entertainment company is an organization that creates, manages, and delivers recreational, cultural, and amusement experiences to consumers through venues, events, media, or activities designed for enjoyment and relaxation.
-
B.
social gaming company
chosen
A social gaming company is an organization that develops and operates games designed to be played and shared with others, emphasizing online interaction, community features, and social engagement among players.
-
C.
entertainment holding company
An entertainment holding company is a parent corporation that owns and manages controlling interests in multiple entertainment-related businesses, such as film studios, music labels, streaming platforms, and live event producers, to coordinate strategy and maximize overall value.
-
D.
sports entertainment group
A sports entertainment group is an organization that creates, manages, and promotes live and media-based sports-related events and content to engage and entertain audiences.
-
E.
sports and entertainment company
A sports and entertainment company is an organization that creates, manages, and promotes athletic competitions, live events, media content, and related experiences for audiences and fans.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
Created at: April 10, 2026, 1:39 p.m.