Triple
T27062260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ゆうパック |
E685075
|
entity |
| Predicate | 運送主体 |
P157981
|
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.
shipCompany
chosen
Indicates that one entity is the shipping company responsible for transporting goods or providing shipping services for another entity.
-
B.
primaryCargoOperator
Indicates that an entity serves as the main organization responsible for operating or managing the cargo-related activities of another entity.
-
C.
commercialCargoProvider
Indicates that an entity serves as a provider of commercial cargo transport or delivery services for another entity.
-
D.
transportedWith
Indicates that one entity was moved or carried together with another entity as part of the same transport event.
-
E.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
- 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.