Triple
T27062255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ゆうパック |
E685075
|
entity |
| Predicate | サービス範囲 |
P104835
|
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.
serviceCovered
Indicates that a particular service is included within the scope, benefits, or obligations defined by a given plan, agreement, or coverage.
-
B.
areaOfService
chosen
Indicates the geographic or functional region within which a service is provided or applicable.
-
C.
serviceAreaName
Indicates the designated name of the geographic or functional area that a service covers or operates within.
-
D.
serviceFor
Indicates that one entity provides a service or performs functions on behalf of another entity.
-
E.
hasServiceAreas
Indicates that an entity provides services within, or is operational across, specific geographic or functional areas.
- 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.