Triple

T592549
Position Surface form Disambiguated ID Type / Status
Subject Leatherhead E17307 entity
Predicate isCommuterHubFor P13163 FINISHED
Object London area 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: London area | Statement: [Leatherhead, isCommuterHubFor, London area]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isCommuterHubFor
Context triple: [Leatherhead, isCommuterHubFor, London area]
  • A. isCommuterRegionFor chosen
    Indicates that one region primarily serves as a residential base whose inhabitants regularly travel to another region for work or daily activities.
  • B. hasTransportHub
    Indicates that a location contains or serves as a central facility where multiple transport routes or modes connect for passenger or cargo movement.
  • C. isResidentialHubIn
    Indicates that a location functions primarily as a residential center or hub within a specified larger area or region.
  • D. hasCommuterOrientation
    Indicates that an entity is designed or intended primarily for use by commuters, emphasizing suitability for regular travel between home and work or study.
  • E. isRailHubFor
    Indicates that a location functions as a central node or interchange point within a rail network for the referenced area, routes, or services.
  • 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_69a49379d09c8190ac7e00b24e2810b1 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a49bbcaf5c81908de4e27096d3da13 completed March 1, 2026, 8:04 p.m.
PD Predicate disambiguation batch_69a494cd7d3c8190af008acf34a2293b completed March 1, 2026, 7:34 p.m.
Created at: March 1, 2026, 7:33 p.m.