Triple
T27062351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | レターパック |
E685077
|
entity |
| Predicate | 料金体系 |
P32811
|
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.
fareStructure
chosen
Indicates the pricing scheme or set of rules that determine how fares are calculated and applied for a given service or trip.
-
B.
feeComponents
Indicates that a fee is composed of one or more sub-fees or cost elements that together make up the total charge.
-
C.
feeType
Indicates the specific category or classification of a fee associated with a transaction, service, or obligation.
-
D.
feePolicy
Indicates the rules or conditions that determine how fees are calculated, applied, or charged in a given context.
-
E.
priceType
Indicates the classification or category of a price associated with an entity (e.g., list price, sale price, wholesale price).
- 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_69f620e0b37481909a280574decbd443 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 8:22 a.m.