Triple
T4614099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinder |
E100825
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | mobile dating application |
C15460
|
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: mobile dating application Context triple: [Tinder, instanceOf, mobile dating application]
-
A.
mobile application feature
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.
-
B.
mobile banking application
A mobile banking application is a secure software platform that enables users to manage their financial accounts, perform transactions, and access banking services directly from their mobile devices.
-
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.
Android application
chosen
An Android application is a software program designed to run on the Android operating system, providing specific functionality or services to users through a mobile or other Android-powered device.
-
E.
mobile device tracking service
A mobile device tracking service is a system that continuously monitors, records, and reports the real-time or historical locations and movement patterns of mobile devices for purposes such as security, analytics, and asset management.
- 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_69bd43cf363c819087fd5ab441b4a3f4 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:12 p.m.