Triple

T26595420
Position Surface form Disambiguated ID Type / Status
Subject Benfleet E667476 entity
Predicate distanceToLondonApproxKm P8256 FINISHED
Object 48 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: 48 | Statement: [Benfleet, distanceToLondonApproxKm, 48]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: distanceToLondonApproxKm
Context triple: [Benfleet, distanceToLondonApproxKm, 48]
  • A. distanceToLondon chosen
    Indicates the measured distance between a given entity’s location and the city of London.
  • B. approximateDistanceKm
    Indicates the estimated distance between two entities measured in kilometers, typically with some degree of inaccuracy or approximation.
  • C. distanceFromCentralLondon
    Indicates the spatial separation or length of travel between a given location and central London.
  • D. distanceToEdinburgh_km
    Indicates the physical distance, measured in kilometers, between an entity’s location and Edinburgh.
  • E. distanceFromHeathrow
    Indicates the measured spatial distance between a given entity and Heathrow.
  • 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_69ee9cfc385081909ac9ae178030a06e completed April 26, 2026, 11:17 p.m.
NER Named-entity recognition batch_69fe7bfc94bc81909eeec946e8c1c450 completed May 9, 2026, 12:12 a.m.
PD Predicate disambiguation batch_69fe7b74a1188190886f128e07f712da completed May 9, 2026, 12:10 a.m.
Created at: April 27, 2026, 2:10 a.m.