Triple
T27062280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ゆうパック |
E685075
|
entity |
| Predicate | 配達方法 |
P15886
|
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.
deliverySystem
Indicates a system, method, or mechanism by which something (such as a product, service, or substance) is transported, distributed, or conveyed from a source to a recipient.
-
B.
ballDeliveryMethod
Indicates the manner or technique by which a ball is delivered, passed, or thrown from one entity to another.
-
C.
deliveryModelOf
Indicates that one entity functions as the delivery model or mechanism through which another entity (such as a service, product, or program) is provided or made available.
-
D.
deliveryStyle
Indicates the manner or approach with which something (such as information, a product, or a service) is presented, communicated, or provided to its recipient.
-
E.
deliveryType
chosen
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
- 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_69ef14835fcc81908bd737b4267ae528 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f622e5c8e4819090baecc212ac8a21 |
completed | May 2, 2026, 4:14 p.m. |
| PD | Predicate disambiguation | batch_69f61b3ee7b08190a0a1bc5d26b757aa |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 8:22 a.m.