Triple

T27265370
Position Surface form Disambiguated ID Type / Status
Subject Yokohama Minatomirai Railway Company E687885 entity
Predicate primaryRailwayLine P848 FINISHED
Object Minatomirai Line 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: Minatomirai Line | Statement: [Yokohama Minatomirai Railway Company, primaryRailwayLine, Minatomirai Line]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryRailwayLine
Context triple: [Yokohama Minatomirai Railway Company, primaryRailwayLine, Minatomirai Line]
  • A. railwayLine chosen
    Indicates that there is a railway line connection or route associated with or passing through the referenced entity.
  • B. formerRailwayLine
    Indicates that a railway line previously existed in the past but is no longer in operation or has been decommissioned.
  • C. originalRailway
    Indicates that a railway is the first or initial line from which others in a network, route, or system originate or are derived.
  • D. railwayLineType
    Indicates the specific kind or classification of a railway line associated with an entity (e.g., main line, branch line, high-speed line).
  • E. primaryRailLinkFor
    Indicates that one entity serves as the main or principal rail connection or route for 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_69ef3557abc481908bf3c146f0f3356a completed April 27, 2026, 10:07 a.m.
NER Named-entity recognition batch_69ff2636e2bc8190bba91eff91431c6e completed May 9, 2026, 12:19 p.m.
PD Predicate disambiguation batch_69ff25c65be48190868480d94e1c4e89 completed May 9, 2026, 12:17 p.m.
Created at: April 27, 2026, 10:55 a.m.