Triple
T27835789
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | エポスカード |
E703221
|
entity |
| Predicate | 付帯サービス |
P163396
|
FINISHED |
| Object | エポスNetによるオンライン会員サービス |
—
|
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: エポスNetによるオンライン会員サービス | Statement: [エポスカード, 付帯サービス, エポスNetによるオンライン会員サービス]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 付帯サービス Context triple: [エポスカード, 付帯サービス, エポスNetによるオンライン会員サービス]
-
A.
carriedServices
Indicates that one entity provides, transports, or delivers specific services on behalf of or in support of another entity.
-
B.
周辺機能
chosen
Indicates a relationship where something provides or relates to auxiliary or surrounding functions/features that support a main function or system.
-
C.
paidTierIncludes
Indicates that a paid subscription tier encompasses or provides access to a specified feature, service, or benefit.
-
D.
promotedService
Indicates that one entity actively markets, advertises, or otherwise promotes a particular service to others.
-
E.
fareIncludes
Indicates that a given fare covers or contains specific components, services, or conditions as part of its overall offering.
- 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_69ef840b94b08190950a4f77296938b2 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641def1e88190a05bf865ced78b23 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 5:59 p.m.