Triple
T33077069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | スカイライナー |
E846393
|
entity |
| Predicate | ブランド名導入 |
P21766
|
FINISHED |
| Object | 「スカイライナー」名称は成田空港アクセス特急の愛称として用いられる |
—
|
NE NERFINISHED |
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.
brand
Indicates that one entity is the commercial brand or label under which another entity (such as a product, service, or organization) is marketed or identified.
-
B.
brandIncorporatedInto
Indicates that one brand has been merged into, absorbed by, or otherwise formally integrated as part of another brand.
-
C.
brandingIntroduced
chosen
Indicates that a particular branding or brand identity has been newly introduced or brought into use for an entity.
-
D.
exportBrand
Indicates a relationship where a brand is sold or distributed outside its home market into foreign or international markets.
-
E.
brandingCategory
Indicates the classification of an entity into a specific branding-related category or type.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 1:25 a.m.