Triple

T35396040
Position Surface form Disambiguated ID Type / Status
Subject St Augustine's Reach E1023079 entity
Predicate adjacentTo P224 FINISHED
Object Canons Road
Canons Road is a street in central Bristol, England, situated along the harbourside near St Augustine’s Reach and known for its mix of cultural venues, restaurants, and waterfront access.
E2296119 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: Canons Road | Statement: [St Augustine's Reach, adjacentTo, Canons Road]
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: Canons Road
Triple: [St Augustine's Reach, adjacentTo, Canons Road]
Generated description
Canons Road is a street in central Bristol, England, situated along the harbourside near St Augustine’s Reach and known for its mix of cultural venues, restaurants, and waterfront access.

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_69f76df34ba48190bd80f0814cdcd540 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f79535977881909bc8a562ed19c6d6 completed May 3, 2026, 6:34 p.m.
NED1 Entity disambiguation (via context triple) batch_6a823779c36881909ea13897aca80956 completed Aug. 16, 2026, 10:19 p.m.
NEDg Description generation batch_6a8237f0aa40819084b60074cc4379aa completed Aug. 16, 2026, 10:21 p.m.
NED2 Entity disambiguation (via description) batch_6a823854ca788190a1a3fcac804565df completed Aug. 16, 2026, 10:23 p.m.
Created at: May 3, 2026, 4:03 p.m.