Triple
T27835761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | エポスカード |
E703221
|
entity |
| Predicate | 主要利用シーン |
P106649
|
FINISHED |
| Object | 公共料金支払い |
—
|
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: 公共料金支払い | Statement: [エポスカード, 主要利用シーン, 公共料金支払い]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 主要利用シーン Context triple: [エポスカード, 主要利用シーン, 公共料金支払い]
-
A.
isPrimarilyUsedAs
Indicates that one entity serves mainly or most commonly in the role, function, or purpose specified by the other entity.
-
B.
primaryUseOf
Indicates that one entity serves as the main or principal function, purpose, or application of another entity.
-
C.
primaryUseArea
chosen
Indicates the main functional area or domain in which an entity is primarily used or applied.
-
D.
usedPrimarilyIn
Indicates that something is mainly or most commonly employed within a particular context, domain, or purpose.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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.