Triple

T19370908
Position Surface form Disambiguated ID Type / Status
Subject Moorgate to Hertford North E484532 entity
Predicate historicalRouteName P135682 FINISHED
Object Hertford Loop suburban services to Moorgate 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: Hertford Loop suburban services to Moorgate | Statement: [Moorgate to Hertford North, historicalRouteName, Hertford Loop suburban services to Moorgate]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: historicalRouteName
Context triple: [Moorgate to Hertford North, historicalRouteName, Hertford Loop suburban services to Moorgate]
  • A. historicRoute
    Indicates that a route has historical significance, typically due to its age, past usage, or role in notable events.
  • B. nearHistoricalRoute
    Indicates that one entity is located close to a historically significant route or pathway.
  • C. hasHistoricalRoute
    Indicates that an entity possesses or is associated with a route that has historical significance or origin.
  • D. regionHistoricalName
    Indicates that a region has been known by a particular historical name during some past period.
  • E. historicalNameGivenBy
    Indicates that one entity is the name historically assigned to another entity by a specific source, culture, or period.
  • F. None of above. chosen

Provenance (4 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_69d8e8d305088190ad13571532aa454c completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e619b09ef08190a8b420316c0b8eb3 completed April 20, 2026, 12:18 p.m.
PD Predicate disambiguation batch_69e4fd54f8e48190956e73dd8969164a completed April 19, 2026, 4:05 p.m.
PDg Predicate description generation batch_69e5004c23308190a087b7941a90725f completed April 19, 2026, 4:18 p.m.
Created at: April 10, 2026, 1:35 p.m.