Triple

T21568593
Position Surface form Disambiguated ID Type / Status
Subject London & South East sector of British Rail E532224 entity
Predicate operatedServicesFrom P6304 FINISHED
Object commuter towns in Kent 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 towns in Kent | Statement: [London & South East sector of British Rail, operatedServicesFrom, commuter towns in Kent]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatedServicesFrom
Context triple: [London & South East sector of British Rail, operatedServicesFrom, commuter towns in Kent]
  • A. operatedFrom
    Indicates that an entity conducted its activities or operations starting from or based at a particular location or source.
  • B. operatesService
    Indicates that an agent runs, manages, or provides a particular service.
  • C. operatesServiceTo chosen
    Indicates that one entity runs or provides a transportation or service route to another entity or location.
  • D. operatedAmong
    Indicates that an entity carried out operations or activities within, or in coordination with, a specified group, set, or collection of other entities.
  • E. operatedAs
    Indicates that an entity functioned or was used in the capacity, role, or identity of another entity for some period of time.
  • 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_69e0c460db088190828c64206a450273 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69eee9cad95c8190ab165ced6f242302 completed April 27, 2026, 4:44 a.m.
PD Predicate disambiguation batch_69e6320c8c2c81908bf031447d66a052 completed April 20, 2026, 2:02 p.m.
Created at: April 16, 2026, 6:30 p.m.