Triple

T682295
Position Surface form Disambiguated ID Type / Status
Subject Brentford E13207 entity
Predicate hasTransportFeature P8159 FINISHED
Object good road links to central London 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: good road links to central London | Statement: [Brentford, hasTransportFeature, good road links to central London]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTransportFeature
Context triple: [Brentford, hasTransportFeature, good road links to central London]
  • A. hasFeature
    Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
  • B. hasTransportFunction
    Indicates that an entity serves to move or carry something (such as people, goods, or signals) from one place or state to another.
  • C. transmissionTypeSupported
    Indicates that a particular type of transmission is compatible with or can be used by a given system, device, or component.
  • D. supportsFeature
    Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
  • E. transportCharacteristic chosen
    Indicates a relationship where a specific characteristic, property, or feature is attributed to a mode or instance of transport.
  • 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_69a4933e0f98819097d22766c49b61b8 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a4a06f9ee88190a2d757aacd8e3f5b completed March 1, 2026, 8:24 p.m.
PD Predicate disambiguation batch_69a49d1f0ccc819088c1527beabcb718 completed March 1, 2026, 8:10 p.m.
Created at: March 1, 2026, 7:36 p.m.