Triple

T7265707
Position Surface form Disambiguated ID Type / Status
Subject 0 Series Shinkansen E159767 entity
Predicate finalWithdrawalFromService P21869 FINISHED
Object 2008 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: 2008 | Statement: [0 Series Shinkansen, finalWithdrawalFromService, 2008]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: finalWithdrawalFromService
Context triple: [0 Series Shinkansen, finalWithdrawalFromService, 2008]
  • A. withdrawalType
    Indicates the specific method or category by which a withdrawal is carried out in a given context.
  • B. withdrewFrom
    Indicates that one entity removed itself or its participation from another entity, context, or arrangement it was previously part of.
  • C. publicServiceRemit
    Indicates that an entity has an official obligation or mandate to provide services in the public interest, typically under a defined public-service framework or regulation.
  • D. originalServiceEnded chosen
    Indicates that a previously existing or initial service has come to an end or has been terminated.
  • E. withdrawalAnnouncedBy
    Indicates that an entity’s withdrawal (e.g., from an agreement, position, or situation) has been publicly announced or declared by a specified agent or source.
  • 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_69c68838f9948190875fd60b2351230c completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6eb088dac8190b353f6ea3d686025 completed March 27, 2026, 8:39 p.m.
PD Predicate disambiguation batch_69c6e76876608190ac4652bc7153302e completed March 27, 2026, 8:24 p.m.
Created at: March 27, 2026, 2:57 p.m.