Triple
T18643841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Match.com |
E455753
|
entity |
| Predicate | hasTermsOfService |
P118242
|
FINISHED |
| Object | online terms of use |
—
|
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: online terms of use | Statement: [Match.com, hasTermsOfService, online terms of use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTermsOfService Context triple: [Match.com, hasTermsOfService, online terms of use]
-
A.
hasTermsOfUse
chosen
Indicates that an entity is associated with or governed by specific terms of use.
-
B.
termOfService
Indicates that one entity defines or specifies the terms of service (rules, conditions, and usage policies) that apply to another entity.
-
C.
hasAgreementSystem
Indicates that there exists a specific grammatical agreement system (e.g., for features like number, gender, or person) associated with the given entity.
-
D.
hasServiceTo
Indicates that one entity provides, offers, or operates a service for or directed toward another entity.
-
E.
surrenderTerms
Indicates the conditions or stipulations under which one party formally yields or capitulates to another.
- 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.