Triple

T9400572
Position Surface form Disambiguated ID Type / Status
Subject Carentan station E226455 entity
Predicate servesLocalTransport P60095 FINISHED
Object regional trains 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: regional trains | Statement: [Carentan station, servesLocalTransport, regional trains]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesLocalTransport
Context triple: [Carentan station, servesLocalTransport, regional trains]
  • A. servesLocalTrains chosen
    Indicates that a station or facility provides service or stops specifically for local (non-express) train routes.
  • B. transportationServedBy
    Indicates that a transportation facility, route, or area is provided service or coverage by a specific transportation provider or mode.
  • C. coordinatesTransportationServicesWith
    Indicates that one entity organizes and manages the alignment and collaboration of transportation services with another entity or set of entities.
  • D. hasTransportRoute
    Indicates that there exists a designated transportation connection or route linking one entity to another.
  • E. servesRidersTraveling
    Indicates that a service or entity provides transportation-related service or support to riders who are currently traveling or in transit.
  • 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_69ca843170f88190800a8ab2b5fc568e completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd5156b9588190bafb6b1c3ee3c0ed completed April 1, 2026, 5:09 p.m.
PD Predicate disambiguation batch_69cca545b2448190a4297312e39c21ac completed April 1, 2026, 4:55 a.m.
Created at: March 30, 2026, 7:46 p.m.