Triple
T18643752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grindr |
E455752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | LGBT-focused social network |
C9207
|
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: LGBT-focused social network Context triple: [Grindr, instanceOf, LGBT-focused social network]
-
A.
LGBTQ+ pride event
An LGBTQ+ pride event is a public gathering or celebration that promotes visibility, acceptance, and rights for lesbian, gay, bisexual, transgender, queer, and other sexual and gender minority communities through parades, performances, speeches, and community activities.
-
B.
LGBT landmark
An LGBT landmark is a historically or culturally significant place associated with the lives, struggles, achievements, or community spaces of lesbian, gay, bisexual, and transgender people.
-
C.
LGBTQ+ awareness month
LGBTQ+ Awareness Month is a dedicated period of time focused on educating about LGBTQ+ identities and histories, promoting acceptance and inclusion, and advocating for the rights and well-being of LGBTQ+ individuals.
-
D.
collaborative online platform
chosen
A collaborative online platform is a digital environment that enables multiple users to work together in real time or asynchronously by sharing information, coordinating tasks, and communicating through integrated tools and services.
-
E.
LGBT district
An LGBT district is an urban neighborhood or area known for its concentration of lesbian, gay, bisexual, and transgender residents, businesses, cultural institutions, and nightlife, serving as a social and political hub for the LGBT community.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.