Triple

T1245200
Position Surface form Disambiguated ID Type / Status
Subject Oxted E26747 entity
Predicate locatedOn P40 FINISHED
Object A25 road E19429 NE 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: A25 road | Statement: [Oxted, locatedOn, A25 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: A25 road
Context triple: [Oxted, locatedOn, A25 road]
  • A. A25 road chosen
    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.
  • B. A22 road
    The A22 road is a major route in southeast England connecting London with Eastbourne on the south coast.
  • C. A21 road
    The A21 road is a major route in southeast England that connects London with Hastings on the south coast, passing through Kent and East Sussex.
  • D. A29 road
    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.
  • 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 (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_69a4948689d08190b3a4a3f388c02148 completed March 1, 2026, 7:33 p.m.
NER Named-entity recognition batch_69a4bf6498948190b30b09d845d67ac4 completed March 1, 2026, 10:36 p.m.
NED1 Entity disambiguation (via context triple) batch_69b31983cab08190afcd168864c9ccf2 completed March 12, 2026, 7:52 p.m.
Created at: March 1, 2026, 7:47 p.m.