Triple

T7448236
Position Surface form Disambiguated ID Type / Status
Subject Senkawa Station E171937 entity
Predicate FukutoshinLineServiceStarted P49268 FINISHED
Object 2008-06-14 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-06-14 | Statement: [Senkawa Station, FukutoshinLineServiceStarted, 2008-06-14]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: FukutoshinLineServiceStarted
Context triple: [Senkawa Station, FukutoshinLineServiceStarted, 2008-06-14]
  • A. hasAdjacentStationOnFukutoshinLine
    Indicates that one station is directly next to another station along the Fukutoshin railway line.
  • B. throughServiceToLine
    Indicates that a service operates through or along a specified line, establishing a through-service relationship between the service and the line.
  • C. lineServed
    Indicates that a particular transportation line (such as a bus, train, or metro line) provides service to or is operated at a given stop, station, or route segment.
  • D. servesLineSince chosen
    Indicates that a transportation service or route has been operating on a particular line since a specified point in time.
  • E. servedByLine
    Indicates that a transportation stop, station, or location is provided service by a specific transit line.
  • 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_69c68a65402881908f7869368eb746fb completed March 27, 2026, 1:47 p.m.
NER Named-entity recognition batch_69c6f38808fc8190b27a2b455155cb5b completed March 27, 2026, 9:15 p.m.
PD Predicate disambiguation batch_69c6f039f7248190bb4183f97b605763 completed March 27, 2026, 9:01 p.m.
Created at: March 27, 2026, 3:14 p.m.