Triple

T30587323
Position Surface form Disambiguated ID Type / Status
Subject Clapham Road E778551 entity
Predicate servedArea P82 FINISHED
Object Clapham High Street area
The Clapham High Street area is a lively commercial and social hub in Clapham, London, known for its shops, bars, restaurants, and proximity to local transport links.
 E1922086 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: Clapham High Street area | Statement: [Clapham Road, servedArea, Clapham High Street area]
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: Clapham High Street area
Triple: [Clapham Road, servedArea, Clapham High Street area]
Generated description
The Clapham High Street area is a lively commercial and social hub in Clapham, London, known for its shops, bars, restaurants, and proximity to local transport links.

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_69f224a04b248190b0ca443ec86207b8 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f68977c2148190bc9679fdc90ff482 completed May 2, 2026, 11:32 p.m.
NED1 Entity disambiguation (via context triple) batch_6a28571077088190a1aba6fb63263f83 completed June 9, 2026, 6:10 p.m.
NEDg Description generation batch_6a28594a96708190be0c4f1c4b18fccb completed June 9, 2026, 6:19 p.m.
NED2 Entity disambiguation (via description) batch_6a285d23431881908ba2c38328d4cfb8 completed June 9, 2026, 6:36 p.m.
Created at: April 29, 2026, 8:24 p.m.