Triple
T18643586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinder U college mode |
E455748
|
entity |
| Predicate | userVerificationMethod |
P4965
|
FINISHED |
| Object | university email verification |
—
|
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: university email verification | Statement: [Tinder U college mode, userVerificationMethod, university email verification]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: userVerificationMethod Context triple: [Tinder U college mode, userVerificationMethod, university email verification]
-
A.
confirmationMethod
chosen
Indicates the means or process by which something is verified, validated, or confirmed as true or accepted.
-
B.
cardVerificationMethod
Indicates the method or process used to verify the authenticity or validity of a card during a transaction or interaction.
-
C.
supportsSignInMethod
Indicates that one entity enables or allows another entity to use a particular sign-in or authentication method.
-
D.
verificationSystem
Indicates that an entity functions as or is associated with a system responsible for checking, validating, or confirming the correctness or authenticity of something.
-
E.
verificationStatus
Indicates whether an entity, claim, or item has been checked and confirmed as authentic, accurate, or compliant according to a defined verification process.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5500b6d7c8190b807b772980d913c |
completed | April 19, 2026, 9:58 p.m. |
| PD | Predicate disambiguation | batch_69e478d85864819093cbad5ed9b54878 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.