Triple

T33077086
Position Surface form Disambiguated ID Type / Status
Subject スカイライナー E846393 entity
Predicate 運行ダイヤ特徴 P89574 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. trainOperation
    Indicates that an entity is engaged in operating, running, or managing the movement and service of a train.
  • B. operationalCharacteristic chosen
    Indicates a relationship where a specific functional or performance trait is attributed to, or used to describe, how an entity operates.
  • C. transportationCharacteristic
    Indicates a specific property, feature, or quality that characterizes a mode, means, or instance of transportation.
  • D. transportCharacteristic
    Indicates a relationship where a specific characteristic, property, or feature is attributed to a mode or instance of transport.
  • E. operatesRailNetworkOf
    Indicates that one entity manages and runs the rail network belonging to or associated with another entity.
  • 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.