Triple

T27550986
Position Surface form Disambiguated ID Type / Status
Subject Old Oak Common E695497 entity
Predicate locatedOn P40 FINISHED
Object Old Oak Common Lane
Old Oak Common Lane is a road in West London that serves the Old Oak Common area, providing access to local rail facilities and surrounding neighborhoods.
 E1777660 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: Old Oak Common Lane | Statement: [Old Oak Common, locatedOn, Old Oak Common Lane]
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: Old Oak Common Lane
Triple: [Old Oak Common, locatedOn, Old Oak Common Lane]
Generated description
Old Oak Common Lane is a road in West London that serves the Old Oak Common area, providing access to local rail facilities and surrounding neighborhoods.

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_69ef5386c3e08190bfe33aa326e1f72b completed April 27, 2026, 12:16 p.m.
NER Named-entity recognition batch_69f62f8b88c88190a327896be2af2f06 completed May 2, 2026, 5:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a12c5c6a48c8190806aa0c850834de9 completed May 24, 2026, 9:32 a.m.
NEDg Description generation batch_6a12c6f592908190a6925a9c563dfdb0 completed May 24, 2026, 9:37 a.m.
NED2 Entity disambiguation (via description) batch_6a12c7a235f08190909cbd31986349d4 completed May 24, 2026, 9:40 a.m.
Created at: April 27, 2026, 1:34 p.m.