Triple

T3223252
Position Surface form Disambiguated ID Type / Status
Subject Liverpool Road E67557 entity
Predicate hasTransportHistorySignificance P46623 FINISHED
Object early railway development in Britain 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: early railway development in Britain | Statement: [Liverpool Road, hasTransportHistorySignificance, early railway development in Britain]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransportHistorySignificance
Context triple: [Liverpool Road, hasTransportHistorySignificance, early railway development in Britain]
  • A. hasTransportHistory
    Indicates that there exists a record or sequence of past transportation-related events or movements associated with an entity.
  • B. hasTransportHistoryAs
    Indicates that an entity has a record or log of being transported, characterized or classified in a specific way.
  • C. hasHistoryOf
    Indicates that an entity has a documented prior occurrence or background of a specified condition, event, or state.
  • D. hasTypeHistory
    Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
  • E. hasFireHistory
    Indicates that an entity has experienced one or more fire events in the past.
  • 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_69ad858b8adc8190ad989712c87a476b completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69adae196da8819086fdcf5d2b21a702 completed March 8, 2026, 5:12 p.m.
PD Predicate disambiguation batch_69ad9e0bb6c48190a0659c67d40ee37c completed March 8, 2026, 4:04 p.m.
PDg Predicate description generation batch_69ada148e9108190b363dd0f1a94ac8e completed March 8, 2026, 4:18 p.m.
Created at: March 8, 2026, 3:08 p.m.