Triple
T4614132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinder |
E100825
|
entity |
| Predicate | secondaryUseCase |
P2114
|
FINISHED |
| Object | casual dating |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: casual dating | Statement: [Tinder, secondaryUseCase, casual dating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryUseCase Context triple: [Tinder, secondaryUseCase, casual dating]
-
A.
secondaryFunction
chosen
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
B.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
C.
secondaryActivity
Indicates that an entity engages in an additional, non-primary activity or role alongside its main activity.
-
D.
secondaryMethod
Indicates that an entity serves as an additional or backup method used alongside or after a primary method in performing an action or achieving a result.
-
E.
secondaryLandUse
Indicates a secondary or additional way in which a piece of land is used, beyond its primary designated use.
- F. None of above.
Provenance (3 batches)
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. |
| NER | Named-entity recognition | batch_69bd59c2678c8190ab8f9420e866521d |
completed | March 20, 2026, 2:29 p.m. |
| PD | Predicate disambiguation | batch_69bd522e2d5c8190937d0b5574f78f99 |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:12 p.m.