Triple

T2143949
Position Surface form Disambiguated ID Type / Status
Subject Penge E47020 entity
Predicate locatedOn P40 FINISHED
Object A213 road
The A213 road is a main route in south London that connects several districts, including Penge, and links local traffic to larger arterial roads.
 E574981 NE FINISHED

How this triple was built (4 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: A213 road | Statement: [Penge, locatedOn, A213 road]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: A213 road
Context triple: [Penge, locatedOn, A213 road]
  • A. A215 road
    The A215 road is a major route in south London, England, connecting several inner-city districts between central London and the suburbs.
  • B. A217 road
    The A217 road is a major route in southeast England that connects the town of Reigate with other parts of Surrey and Greater London.
  • 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. A232 road
    The A232 road is a major east–west route in South London and northwest Kent, connecting several suburbs and towns between Orpington and Ewell.
  • 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. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: A213 road
Triple: [Penge, locatedOn, A213 road]
Generated description
The A213 road is a main route in south London that connects several districts, including Penge, and links local traffic to larger arterial roads.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07 
Target entity: A213 road
Target entity description: The A213 road is a main route in south London that connects several districts, including Penge, and links local traffic to larger arterial roads.
  • A. A215 road
    The A215 road is a major route in south London, England, connecting several inner-city districts between central London and the suburbs.
  • B. A217 road
    The A217 road is a major route in southeast England that connects the town of Reigate with other parts of Surrey and Greater London.
  • 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. A232 road
    The A232 road is a major east–west route in South London and northwest Kent, connecting several suburbs and towns between Orpington and Ewell.
  • 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. chosen

Provenance (5 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_69a88a1933e0819094f18426ed74180f completed March 4, 2026, 7:38 p.m.
NER Named-entity recognition batch_69abbe223f848190a60bd0f15aed1021 completed March 7, 2026, 5:56 a.m.
NED1 Entity disambiguation (via context triple) batch_69c16e581e94819086313b9d3a40b159 completed March 23, 2026, 4:46 p.m.
NEDg Description generation batch_69c1e023cfd0819089cb5727c673f098 completed March 24, 2026, 12:51 a.m.
NED2 Entity disambiguation (via description) batch_69c1e07df8388190ba0ed8879a4ca2ee completed March 24, 2026, 12:53 a.m.
Created at: March 4, 2026, 7:44 p.m.