Triple
T27062361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | レターパック |
E685077
|
entity |
| Predicate | 運送事業者 |
P34619
|
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
Indicates that one entity is the shipping company responsible for transporting goods or providing shipping services for another entity.
-
B.
commercialCargoProvider
Indicates that an entity serves as a provider of commercial cargo transport or delivery services for another entity.
-
C.
freightSubsidiary
Indicates that one entity is a subsidiary company specifically involved in freight or cargo operations for another entity.
-
D.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
-
E.
transportOperator
chosen
Indicates that an entity is responsible for operating or managing the transportation of people or goods between locations.
- 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.