Triple
T27835790
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | エポスカード |
E703221
|
entity |
| Predicate | 申込方法 |
P18002
|
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.
submissionMethod
chosen
Indicates the means or channel through which something is submitted or delivered.
-
B.
attachmentMethod
Indicates the way or technique by which one entity is fastened, joined, or secured to another.
-
C.
canApplyFor
Indicates that one entity has the eligibility or permission to submit a request or application for another entity or opportunity.
-
D.
inscriptionSupport
Indicates that one entity serves as the physical surface or material on which another entity (an inscription) is written, carved, or otherwise recorded.
-
E.
onlineApplication
Indicates that an application or request is submitted, processed, or managed through an online or web-based system.
- 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_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:59 p.m.