Triple

T36293404
Position Surface form Disambiguated ID Type / Status
Subject Eastern Region E893293 entity
Predicate railServicesIncluded P154206 FINISHED
Object commuter services into London 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: commuter services into London | Statement: [Eastern Region, railServicesIncluded, commuter services into London]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: railServicesIncluded
Context triple: [Eastern Region, railServicesIncluded, commuter services into London]
  • A. railServiceType
    Indicates the specific category or type of rail service that applies to the relationship between the involved entities (e.g., local, express, freight).
  • B. hasRailServiceAt chosen
    Indicates that a rail transport service operates at or serves a particular location or facility.
  • C. railServicesTo
    Indicates that rail transportation services operate from one location to another specified destination.
  • D. hasPassengerServicesTo
    Indicates that a transportation provider operates passenger services connecting one location or entity to another.
  • E. isRailServiceOf
    Indicates that a particular rail service operates for, belongs to, or is provided by a specified entity (such as a route, operator, or network).
  • 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_69f76e4a61f0819084a2b68dbbb4efc6 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7ba6d06f48190a71b5a2f19e2232f completed May 3, 2026, 9:13 p.m.
PD Predicate disambiguation batch_69f7b9a4aad48190a62e41c5e39339d9 completed May 3, 2026, 9:09 p.m.
Created at: May 3, 2026, 4:09 p.m.