Triple

T3053399
Position Surface form Disambiguated ID Type / Status
Subject BHM E60422 entity
Predicate regionCodeSystem P45385 FINISHED
Object UK National Rail station code system 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: UK National Rail station code system | Statement: [BHM, regionCodeSystem, UK National Rail station code system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: regionCodeSystem
Context triple: [BHM, regionCodeSystem, UK National Rail station code system]
  • A. regionCodeType
    Indicates the classification or format type used for a given region code within a coding or identification system.
  • B. ISO3166-2RegionCode
    Indicates the standardized ISO 3166-2 code that specifies the particular primary administrative subdivision (such as a state, province, or region) to which an entity belongs.
  • C. commonCRSCode
    Indicates that two or more entities share the same Common Reporting Standard (CRS) code used for tax or financial reporting classification.
  • D. hasAreaCodeSystem
    Indicates that a telephone numbering plan, region, or communication system uses or is associated with a particular area code system.
  • E. subregionCodeFor
    Indicates that one entity is the code assigned to identify a specific subregion of the other entity.
  • 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_69ad8578137c81908259dcb27c7d6d7c completed March 8, 2026, 2:19 p.m.
NER Named-entity recognition batch_69ad9bf3c52c8190bbe8e5cb98c21715 completed March 8, 2026, 3:55 p.m.
PD Predicate disambiguation batch_69ad962195388190856013a2519c2b0f completed March 8, 2026, 3:30 p.m.
PDg Predicate description generation batch_69ad9b272a408190ba0ce09bdeea76c9 completed March 8, 2026, 3:52 p.m.
Created at: March 8, 2026, 3:01 p.m.