Triple

T29573784
Position Surface form Disambiguated ID Type / Status
Subject Tokyo Denki University (near Kita-Senju) E753380 entity
Predicate railLineAccess P57688 FINISHED
Object JR Joban Line via Kita-Senju Station 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: JR Joban Line via Kita-Senju Station | Statement: [Tokyo Denki University (near Kita-Senju), railLineAccess, JR Joban Line via Kita-Senju Station]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railLineAccess
Context triple: [Tokyo Denki University (near Kita-Senju), railLineAccess, JR Joban Line via Kita-Senju Station]
  • A. railAccessModel
    Indicates the type or pattern of how rail infrastructure or services are accessed or connected between locations or entities.
  • B. railwayAccess chosen
    Indicates that an entity has direct access to, connection with, or service by a railway line or station.
  • C. railLineOrigin
    Indicates that a rail line begins or originates from a specified location or point.
  • D. railInfrastructureServed
    Indicates that a rail infrastructure facility or segment is served, accessed, or operated by a particular service, operator, or network.
  • E. railwayLine
    Indicates that there is a railway line connection or route associated with or passing through the referenced 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_69f0ef7fcb4881908a933110adb9bda1 completed April 28, 2026, 5:33 p.m.
NER Named-entity recognition batch_69f66d4896648190b8f42af1996b9bc3 completed May 2, 2026, 9:31 p.m.
PD Predicate disambiguation batch_69f6659d36208190b01412600a4ed57d completed May 2, 2026, 8:59 p.m.
Created at: April 28, 2026, 6 p.m.