Triple
T7715207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Japan Post |
E174861
|
entity |
| Predicate | brand |
P1500
|
FINISHED |
| Object | ゆうパケット (Yu-Packet) |
E685077
|
NE 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: ゆうパケット (Yu-Packet) | Statement: [Japan Post, brand, ゆうパケット (Yu-Packet)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ゆうパケット (Yu-Packet) Context triple: [Japan Post, brand, ゆうパケット (Yu-Packet)]
-
A.
ゆうパック (Yu-Pack)
ゆうパック (Yu-Pack) is Japan Post’s nationwide parcel delivery service for sending packages and gifts domestically and internationally.
-
B.
ゆうメール (Yu-Mail)
ゆうメール (Yu-Mail) is a discounted Japan Post service for sending books and other printed or recorded materials at low cost within Japan.
-
C.
レターパック (Letter Pack)
chosen
レターパック（Letter Pack）は、日本郵便が提供する全国一律料金・追跡可能な封筒型の小型荷物配送サービスブランドです。
-
D.
Parcel
Parcel is a zero-configuration web application bundler known for its fast performance, automatic code splitting, and built-in support for modern JavaScript tooling.
-
E.
Yam postal system
The Yam postal system was an extensive relay network of stations and mounted couriers that enabled rapid communication and administration across the vast Mongol Empire.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c6995c463c8190a14458036249d419 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c702cbe74081908502ac670515fa3c |
completed | March 27, 2026, 10:21 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8be2831788190a8ba7340b5d4d439 |
completed | March 29, 2026, 5:52 a.m. |
Created at: March 27, 2026, 4:04 p.m.