Triple

T34992021
Position Surface form Disambiguated ID Type / Status
Subject Phipps Bridge E1009415 entity
Predicate adjacentTo P224 FINISHED
Object Wandle Valley
Wandle Valley is a green corridor in South London following the River Wandle, known for its parks, nature reserves, and walking and cycling routes through several boroughs.
E2123773 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: Wandle Valley | Statement: [Phipps Bridge, adjacentTo, Wandle Valley]
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: Wandle Valley
Triple: [Phipps Bridge, adjacentTo, Wandle Valley]
Generated description
Wandle Valley is a green corridor in South London following the River Wandle, known for its parks, nature reserves, and walking and cycling routes through several boroughs.

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_69f76dca50dc8190b71f39defe186be8 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f784c00184819097632e1a58d6e39d completed May 3, 2026, 5:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37c625ad88819080620726ff88b3bf completed June 21, 2026, 11:08 a.m.
NEDg Description generation batch_6a37c68ba658819095991b05c97af30c completed June 21, 2026, 11:10 a.m.
NED2 Entity disambiguation (via description) batch_6a37c7800d208190b6c01e8b53dab112 completed June 21, 2026, 11:14 a.m.
Created at: May 3, 2026, 4:01 p.m.