Triple
T18643563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinder U college mode |
E455748
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | online dating service feature |
C11881
|
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: online dating service feature Context triple: [Tinder U college mode, instanceOf, online dating service feature]
-
A.
online dating service
An online dating service is a digital platform that connects individuals seeking romantic or social relationships by matching user profiles based on preferences, interests, and compatibility criteria.
-
B.
online personal styling service
An online personal styling service is a digital platform that curates and recommends clothing and accessories tailored to an individual’s preferences, body type, and lifestyle, often using stylist expertise and/or algorithms.
-
C.
manosphere group
A manosphere group is an online or offline community centered around male identity, gender roles, and men’s issues, often characterized by shared ideologies about masculinity, relationships, and societal power dynamics.
-
D.
mobile application feature
chosen
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.
-
E.
Skype service feature
A Skype service feature is a distinct capability or tool within the Skype platform that enables users to communicate, collaborate, or manage their interactions through functions such as voice and video calls, messaging, file sharing, and screen sharing.
- 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.