Triple

T25305772
Position Surface form Disambiguated ID Type / Status
Subject London to Norwich main line E634477 entity
Predicate majorTownServed P112697 FINISHED
Object Chelmsford NE NERFINISHED

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: Chelmsford | Statement: [London to Norwich main line, majorTownServed, Chelmsford]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: majorTownServed
Context triple: [London to Norwich main line, majorTownServed, Chelmsford]
  • A. townServed
    Indicates that a given service, facility, or infrastructure serves or provides coverage to a particular town.
  • B. majorIntermediateCityServed chosen
    Indicates that a major intermediate city lies along a route or corridor and is served by the associated service or infrastructure.
  • C. modernCityServed
    Indicates that a modern city receives services, support, or functions (such as transportation, utilities, or administration) from a specified provider or infrastructure.
  • D. alternativeCityServed
    Indicates that one city functions as an alternative service location for another city, typically in contexts like transportation or logistics.
  • E. majorTownInRegion
    Indicates that a town is one of the principal or most significant towns within a specified region.
  • 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_69e75a972c6481909bc11710e8d30a6c completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f69383222c81909d8baa04129d5c81 completed May 3, 2026, 12:14 a.m.
PD Predicate disambiguation batch_69f690eb1e948190aab41a89969519a5 completed May 3, 2026, 12:03 a.m.
Created at: April 21, 2026, 1:25 p.m.