Triple

T27896104
Position Surface form Disambiguated ID Type / Status
Subject Putney Bridge Road E705495 entity
Predicate servedByBusRoute P14525 FINISHED
Object London Buses route 337
London Buses route 337 is a Transport for London bus service in southwest London that runs between Richmond and Clapham Junction via key local centres such as Putney.
E1797847 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: London Buses route 337 | Statement: [Putney Bridge Road, servedByBusRoute, London Buses route 337]
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: London Buses route 337
Triple: [Putney Bridge Road, servedByBusRoute, London Buses route 337]
Generated description
London Buses route 337 is a Transport for London bus service in southwest London that runs between Richmond and Clapham Junction via key local centres such as Putney.

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_69ef96b490ac8190a412d04c5d009f3e completed April 27, 2026, 5:02 p.m.
NER Named-entity recognition batch_69f639f4c7c88190ad20ec170606d707 completed May 2, 2026, 5:52 p.m.
NED1 Entity disambiguation (via context triple) batch_6a13114be5fc81908035cc550f1b6d63 completed May 24, 2026, 2:55 p.m.
NEDg Description generation batch_6a1312211af88190ab84fc43b748a93e completed May 24, 2026, 2:58 p.m.
NED2 Entity disambiguation (via description) batch_6a13148cc15c8190928bfe77917e4176 completed May 24, 2026, 3:09 p.m.
Created at: April 27, 2026, 6:38 p.m.