Triple
T27062350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | レターパック |
E685077
|
entity |
| Predicate | サービス形態 |
P59247
|
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.
営業形態
Indicates the manner or mode in which a business operates or conducts its commercial activities.
-
B.
servicesType
Indicates the category or kind of services that one entity provides, uses, or is associated with in relation to another entity.
-
C.
service
Indicates that one entity performs work, assistance, or functions to meet the needs or requests of another entity.
-
D.
serviceIn
Indicates that one entity serves, operates, or performs its function within the context, scope, or domain of another entity.
-
E.
servicePatternOf
chosen
Indicates that one entity is the service pattern (e.g., schedule, routing, or operational configuration) that defines or characterizes how another service-related entity operates.
- 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.