Triple
T27062354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | レターパック |
E685077
|
entity |
| Predicate | 追跡方法 |
P18529
|
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.
trackingType
chosen
Indicates the method or category by which an entity’s movement, status, or progress is monitored or recorded.
-
B.
traceOf
Indicates that one entity is a remaining sign, mark, or residual evidence of the presence, existence, or action of another entity.
-
C.
usesTrackage
Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
-
D.
trackingAvailable
Indicates that tracking information or functionality is available for the associated item, process, or interaction.
-
E.
trackFrom
Indicates a source or origin from which something is tracked or monitored.
- 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.