Triple

T11779169
Position Surface form Disambiguated ID Type / Status
Subject Ockley E280095 entity
Predicate roadAccess P385 FINISHED
Object A29 road NE NERFINISHED

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: A29 road | Statement: [Ockley, roadAccess, A29 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A29 road
Context triple: [Ockley, roadAccess, A29 road]
  • A. A29 road chosen
    The A29 road is a primary route in southern England that runs through West Sussex, connecting several towns and providing an important north–south link between the South Downs and the coastal areas.
  • B. A28 road
    The A28 road is a major route in southeast England that runs through Kent and East Sussex, linking towns such as Ashford and Canterbury.
  • C. A22 road
    The A22 road is a major route in southeast England connecting London with Eastbourne on the south coast.
  • D. A25 road
    The A25 road is an important east–west route in South East England that runs through Surrey and connects several towns between Guildford and Sevenoaks.
  • E. A23 road
    The A23 road is a major route in southern England connecting London to Brighton, serving as a key corridor between the capital and the south coast.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d6ab01d2688190ad8ed6bda487eaa5 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a5623f708190a18aea570577a3f6 completed April 10, 2026, 7:23 a.m.
Created at: April 8, 2026, 9:42 p.m.